Hello all, i have the following job-def:
Job {
Name = "domino"
JobDefs = "DefaultJob"
Storage = Roboter
Schedule = WocheSpaet
Client = domino-fd
Write Bootstrap = "/var/lib/bacula/domino.bsr"
FileSet = "domino"
ClientRunBeforeJob = "/etc/init.d/domino stop"
ClientRunAfterJob = "/sbin/shutdown -r +5"
MaxRunTime = 12600 # max 3.5h}
Because sometimes when intervention is needed the domino stays down, i've added the "MaxRunTime = 12600" line (job needs 2.5h if everything works well)!
We do incremental backups over the week and full backups on weekends. The incremental works well because the job runs nearly the scheduled time! Last weekend (full-backup) the job was chanceld befor it was started (scheduled for 23:59) and i got:
07-May 03:29 sug-bkup-dir: JobId 457, Job domino.2005-05-06_23.59.00 marked to be canceled.
From the dokumentation:
"Max Run Time = <time> The time specifies maximum allowed time that a job may run, counted from the when the job starts (not necessarily the same as when the job was scheduled)."
That could not be true! The job stops after the scheduled time!
Any hints to fix?
Regards, Mario
PS:
the schedule:
Schedule {
Name = "WocheSpaet"
Run = Level=Full fri at 23:59
Run = Level=Incremental mon-thu at 23:59
}Would be nice to have a "noRun" system to exlude working hours!
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
