On Dec 5, 2012, at 12:34 PM, Oliver Hoffmann wrote: > Am Wed, 5 Dec 2012 17:37:57 +0100 > schrieb Oliver Hoffmann <o...@dom.de>: > >>> >>> Zitat von Oliver Hoffmann <o...@dom.de>: >>> >>>> Hi all, >>>> >>>> recently I had the following problem. After a reboot of the bacula >>>> server due to malfunction of the attached RAID all jobs very not >>>> running again. OK, that is what I expected but not what I wanted >>>> as starting 50 or more jobs by hand with bconsole is a bit >>>> tiresome. Thus I simply waited for the next backup run but that >>>> means no backups for that night. >>>> >>>> Is there a way to accomplish a mass restart of >>>> jobs? My first thought was scripting the bconsole but maybe there >>>> is a build-in solution or something easier for that? >>>> >>>> Thx for ideas, >>>> >>>> Oliver >>> >>> You can alter the schedule time used and restart the director, but >>> most of the time starting backup jobs out of the backup window is >>> a bad idea anyway. If the jobs failed instead of get skipped you >>> can have a look at the "Reschedule On Error" jobs setting. >>> >>> Regards >>> >>> Andreas >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Keep yourself connected to Go Parallel: >>> BUILD Helping you discover the best ways to construct your parallel >>> projects. http://goparallel.sourceforge.net >>> _______________________________________________ >>> Bacula-users mailing list >>> Bacula-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/bacula-users >>> >> >> I did some tests. First I stopped the bacula-fd on the client while a >> job was running. The settings on the client: >> >> Reschedule On Error = yes >> Reschedule Interval = 10 minutes >> Reschedule Times = 5
I have similar; Max Start Delay = 2 minutes Reschedule On Error = yes Reschedule Interval = 20 minutes see below… >> >> The result was as expected: >> >> Fatal error: Network error with FD during Backup: ERR=No data >> available JobId 51618: Fatal error: No Job status returned from FD. >> >> That happened at 18:48. The reschedule of the job took place at 20:41. >> Why not at 18:58? There were no other jobs running and the server was >> up and idle. Same for the client. The fd was stopped for a minute or >> less. >> >> Next I rebooted the server while a job was running. A status dir tells >> me "No Jobs running." Status of the client: >> >> JobId 51718 Job client.2012-12-05_16.37.23_06 is running. >> Incremental System or Console Job started: 05-Dez-12 16:37 >> Files=0 Bytes=0 Bytes/sec=0 Errors=0 >> Files Examined=0 >> SDReadSeqNo=3 fd=5 >> Director connected at: 05-Dez-12 17:31 >> >> But nothing happens. Is it buggy or do I miss something here? >> >> Version server: 5.2.5-0ubuntu6.2 >> Version client: 5.2.5 (26 January 2012) x86_64-pc-linux-gnu ubuntu >> 12.04 >> >> Greetings, >> >> Oliver >> >> > Ok, a command before job was blocking. But now it still does not > re-run. Does that mean, that once the server was rebooted all the > reschedules are not taken out? The Reschedule command will not help you if the Director is restarted. -- Dan Langille - http://langille.org ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
