Greetings, a puzzling event occurred to me while deploying bacula. I have the following jobs defined (same priority):
Job {
Name = "Standard backup"
Schedule = "MonthlyCycle"
FileSet = general
...
}Job {
Name = "First backup"
Schedule = "MonthlyCycle"
RunBefore = "/script/stop/first"
RunAfter = "/script/start/first"
FileSet = first
...
}Job {
Name = "Second backup"
Schedule = "MonthlyCycle"
RunBefore = "/script/stop/second"
RunAfter = "/script/start/second"
FileSet = second
...
}all using this schedule
Schedule {
Name = "MonthlyCycle"
Run = Full 1st sun at 3:05
Run = Differential 2nd-5th sun at 3:05
Run = Incremental mon-sat at 3:05
}but the jobs were scheduled as follows:
standard (incremental) Start time: 17-Mar-2005 03:05:02 End time: 17-Mar-2005 03:10:01
first (full) Start time: 17-Mar-2005 03:10:03 End time: 17-Mar-2005 03:13:15
second (full) Start time: 17-Mar-2005 09:55:14 End time: 17-Mar-2005 10:41:32
Why is the second backup launched a few hours later ?
The tape server is a Fedora Core 1 host using an LTO drive. By analogy with cron, I'm about to redirect standard input and output in the
RunBefore and RunAfter to /dev/null, just in case. Any suggestions ?
Thank you for your consideration, Davide Bolcioni -- There is no place like /home.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
