oopsie
So I swapped out the 250gb disk for a 2tb disk, currently cp'ing the
volumes from old to new. How do I get the stalled job to restart? or do I
kill it (if so how?) and just kick off a manual one?
--
___
Not sure if there is such a thing as "a standard bacula configuration", but
as I said, the simple math says that if you only do 1 monthly full backup
and you keep the last year's worth of full backups, you'll need 2.4TB of
storage. This completely ignores the retention of other backup levels.
On
It is a standard bacula configuration at present.
Most of the data will be static as its historic (up to 8 years old) copied
off a mac to a nfs mount and kept for the occasional random access from
other macs.
On 28 October 2015 at 09:51, Thing wrote:
> Hi,
>
> It is a standard bacula configurat
Hi,
It is a standard bacula configuration, data will also not change much. So
from your estimate with compression a 3TB drive would seem the minimum.
On 28 October 2015 at 09:14, John Lockard wrote:
> How often are you backing up? Fulls, Differentials, Incrementals? How
> long do you want to
How often are you backing up? Fulls, Differentials, Incrementals? How
long do you want to keep each? How compressible is your data? How much
does the data change? How often does the data change?
Too many variables to answer your questions as given.
Only full backups, once a month, you'd need
Hi,
To backup 200gb with 1 year retention roughly how big a disk would be
required? 2tb? 3tb?
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.s
Hi,
I had no error it simply ignored it. I later restarted the bacula-fd and
now its backing up /nfs01 though I am about to run out of space on
/bacula/backup! ouch. I didnt expect a 107gb backup when using
compression to fill a 250gb disk by 207gb+ (it has not finished yet) but it
is only a te
On 10/27/15 12:55, Ana Emília M. Arruda wrote:
> Hello Thing,
>
> Could you post the error messages that you get when run the job?
>
> Maybe the "onefs = no" directive should be configured in your fileset.
> The default is yes, so bacula will not descend into different file
> systems and It seems
Sebastian,
First, it’s usually a bad idea to have your FD running a newer version than
your director. That is an unsupported combination and is likely to cause
problems. It can be the other way around, the director can be newer than your
FD. I understand that 5.0.0 is the default carried by
Hello Thing,
Could you post the error messages that you get when run the job?
Maybe the "onefs = no" directive should be configured in your fileset. The
default is yes, so bacula will not descend into different file systems and
It seems your "/" and "nfs01" are different filesystems.
Also, this
Hi bacula users,
we're backing up Windows Server 2008 R2 64bit with Bacula using VSS.
Occasionally we're getting the following error messages:
27-Oct 02:02 HOST JobId 44046: Generate VSS snapshots. Driver=\"Win64 VSS\",
Drive(s)=\"C\"
27-Oct 02:05 HOST JobId 44046: VSS Writer (BackupComplete): \
11 matches
Mail list logo
