Hello,
I'm running Bacula at the office to backup our workstations and some
local servers. Once in a while, a job will block the backup and
eventually, all queued jobs will be cancelled. So, according to
http://www.bacula.org/dev-manual/Configuring_Director.html, you can set
the Max Wait Time, for a particular job. So I added this for each jobs
we have:
Max Wait Time = 10 minutes
So, from my understanding of the documentation, if Job1 blocks the
backup for 10 minutes, Job1 will be cancelled, and bacula should move on
to Job2.
Now, let's get some specific info about our system. We're running the
lastest stable Debian (3.1), bacula-director is 1.36. We're backing up a
mix of Windows machines, linux and BSDs. Clients are also 1.36.
We have 2 JobDefs, 1 for workstations, that start at 7pm, and one for
servers, that runs at 2am.
What happened exactly is this: bacula started to run jobs at 7pm as
usual, and at 7:10pm, it cancelled all remaining jobs from the JobDefs1
(workstations). You can find in that link the relevant part of that
night's logs:
http://pastebin.ca/44343
If you need more info, config files, etc, let me know. Thanks,
--
Jean-Francois Theroux
http://jief.theroux.ca
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
