Hello, I promised to not make any followup to this thread, but below question requires an answer!
wt., 23 kwi 2019 o 16:40 Josh Fisher <jfis...@pvct.com> napisał(a): > but the automated "Reschedule On Error" feature >> allows restarting them after the fail-over. > > > Well, no. Rescheduling is based on actual job thread running on Bacula > Director. Any Director restart will stop this feature for a particular > jobid! > > > Hmm. Then what is the status of a running job that is interrupted by a > Director restart? > When Director starts it checks a catalog database to find any job with Running status. If it finds some it changes its status to Failed. > It is a running job when the Dir is stopped, and is an error job once > restarted. How does that happen? If the job status is updated during > Director startup, then why doesn't the reschedule occur? > Reschedule occur in the job thread loop. To make a reschedule working Director manages some internal variables such as: int32_t reschedule_count; /* Number of times rescheduled */ and reschedule interval as a simple sleep in loop. The reschedule state is not saved, so during Director restart it is impossible to recover this state. 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. It is not implemented now, IMHO. As always YMMV. best regards -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
