Craig,
I suspect this is because the media type for both your Incremental and
Differential pools is "File" so bacula assumes that it can access Incr0169 via
the /backup/Differential device. I got round this by having different media
types for my different file devices, e.g. FileFull, FileDiff
I have a two stage backup, to disk first then to tape using copy jobs. On the
whole this works fine, but occasionally (e.g. when the tape hasn't been
changed) a copy job is still running when the next round of disk backups start.
When this happens, the disk backups don't start because they are
For what it's worth, I have a similar amount of data and settled on a "Maximum
Volume Bytes" of 200G which has been working without any issues for a few
months now.
Cheers,
Ewan
> -Original Message-
> From: Mike Seda [mailto:mas...@stanford.edu]
> Sent: 20 May 2011 18:49
> To: Bacula U
I have a client that has three separate jobs which go to the same storage
daemon so it isn't an inherent limit.
Cheers,
Ewan
> -Original Message-
> From: Jacek Bilski [mailto:jacek.bil...@avalcom.pl]
> Sent: 18 April 2011 11:49
> To: bacula-users@lists.sourceforge.net
> Subject: [Bacula
Within bconsole you can use "status client=myserver-fd" to get most of this
information (where myserver-fd is the name of the file daemon involved in the
backup).
Cheers,
Ewan
> -Original Message-
> From: Hugo Letemplier [mailto:hugo.let...@gmail.com]
> Sent: 11 April 2011 15:37
> To:
I believe that's normal behaviour for copy jobs.
Cheers,
Ewan
> -Original Message-
> From: Gergely Polonkai [mailto:pol...@w00d5t0ck.info]
> Sent: 08 April 2011 17:04
> To: bacula-users@lists.sourceforge.net
> Subject: [Bacula-users] How do I know if a job is actually part of a
> Copy pr
You are right that no priority 10 jobs will get run while there are higher
priority (lower number) jobs running. To run jobs in parallel they need to be
the same priority.
However, to some extent you can control the order using scheduling. Kick off
the important jobs on the hour and the less
The Windows file daemon doesn't use the C:\$WORKSTATION-fd.conf file. That's
just put there as a convenience at install time. You should really be
comparing the server password with the one in the Bacula program directory
(e.g. C:\program files\bacula\bacula-fd.conf).
EMB
> -Original Mes
Maybe you could achieve something similar using include files for the common
options.
EMB
> -Original Message-
> From: Alan Brown [mailto:a...@mssl.ucl.ac.uk]
> Sent: 25 February 2011 19:56
> To: James Woodward
> Cc: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] Jobdef
