Hi,
I've no doubt I will be referred to some part of the manual that I
missed ;).
But I have had a problem for some time now and done nothing about it.....
If a job takes long enough to cause subsequent job(s) to fail with start wait
time exceeded.
(Fatal error: Job cancelled because max start time exceeded)
All jobs thus failed are upgraded to a Full!
Which for me means that when a certain (large) machine chooses to do its full
backup it causes a chain-reaction of subsequent systems doing full backups.
I do however still want a full backup following a genuine failed backup (a
backup that failed after being started that is!).
I have "Rerun Failed Levels" set to Yes.
Can anyone confirm how to stop the upgrading on exceeding start-time happening
Many Thanks
Andrew R Paterson
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
