Op 16/05/2012 11:30, Maria Arrea schreef:
Hello
I am running happily bacula 5.0.3 for 1 year. Last weekend a full job
took too much time, and the rest of backups started too late, on
Monday. I have read several time about the schedule resource, but I
can not find how to "force" and end time for a job. For example, the
full backup of system "development box" should start at 00:01 on
Sundays, but it should be cancelled if has not finished at 17:00, ¿how
can I accomplish that with Bacula?
Regards
Mariatinfo
You should read up on the MaxRunTime and MaxRunSchedTime directives.
They're both directives you can put in a job definition. One limits the
time a job can run *after* it has actually started (so not counting the
time it waits for other jobs or tapes to become available). The second
gives the max amount of time between the scheduled time of the job and
time it had to be cancelled if it's still running.
So in your example case a MaxRunSchedTime = 17h should do the trick.
Regards,
Jeremy
**** DISCLAIMER ****
http://www.schaubroeck.be/maildisclaimer.htm
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
