> > 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 >
Thank you! That is even better than restarting a bunch of Jobs. I think something like try it three or four times every three hours makes sense for my setup. Greetings, Oliver ------------------------------------------------------------------------------ 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
