hi All
On Thursday 21 April 2016 17:00:14 Clark, Patti wrote:
If you are using spooling (recommended) your spool size parameters are used
to control the size of your job spool and the total spool space available.
The example below shows 50GB of job spool size and a total of 1TB of spool
space. You will need to try sizes that are appropriate for your
environment and see what performs best for you. The job spool size when
reached will write to tape at that point. It will continue with spooling
and writing to tape media until the end of data has been reached. Also for
something like a NAS, it’s best to break the backups into more manageable
chunks. Don’t try to backup the entire NAS in one job. And yes, use the
heartbeatinterval feature.
Maximum Spool Size = 1000GB;
Maximum Job Spool Size = 50GB;
Okay your explanation is clearer to me than what is in the manual. I was going
to use Maximum File Size as a way to "chunk" it, even though I was dubious
about it.
Will implement your suggestions, thanks.
You don’t mention which version of Bacula that you are using. If it is
7.4.x is has a resume command that will restart failed jobs roughly from
Versions vary, Director and FD on this machine (Gentoo) are the same, 7.05 but
the NAS boxes are running FreeNas and I had to compile a version for them in
VirtualBox, don't think the FreeBSD releases are at that level yet. Also was
trying to back up a site on the net running CentOS 6, which had it's own
issues. Eventually gave up, could not get the remote FD and local SD to talk
to each other, I think the problem is somewhere between my firewall (IPFire)
and the SD (CentOS 7 on HP server). So now I rsync remote to here and backup
from here. Initial rsync took 20 hours so it's probably better that way.
It would be nice if the various OSs could get their act together and get the
versions in sync :-)
Thanks, Ian
--
Zero 2 Infinity - The net.works
Phone +27-21-975-7273
