On 4/24/19 11:44 AM, Radosław Korzeniewski wrote: > To make a reschedule after restart possible a Director should save > reschedule state in catalog database. It should save the number of > reschedules passed and an exact time when last reschedule pass started to > checks if it is required to continue any rescheduled jobs.
If you have a multi-terabyte job that takes 20 hours to complete, and the backup schedule is every 24 hours, you're better off just leaving it be until the next scheduled backup. I.e. IMO auto-rescheduling failed jobs has bigger problems than persisting the state across director restarts. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
