Hello everyone!

Yesterday I added a new backup job with a run-before-client script. The 
job was scheduled for 22:00. Unfortunately I made a mistake in the 
script, causing it to hang. When it finally crashed, it was 09:00 in the 
morning. Bacula immediately started the next scheduled job which is the 
backup of our production database. The database was correctly shut down 
during the backup and restarted afterwards. Of course my telephone rang 
like a hundred times because applications all over the company crashed.

I know that bacula did exactly what it was supposed to do.

Still I was wondering, whether there was a way to stop bacula from 
running certain jobs in a specific time window, no matter what.
Of course I could try to add some checks to my run-before script keeping 
the database from being shut down at specific times.

All the best,

Nils



-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users