Suspended jobs restart automatically?
Simple, stupid question just to keep you on your toes:
Any reason why a job suspended thru' the Activity Monitor should then literally fail after an undetermined period of time (with Status 157) & restart?
Job initially just sits there as expected in a suspended state. It then fails (big red x) & restarts as a different job id & commences backing up!!!!
Obviously, if I suspend a job I've done it for a reason & therefore would not expect, nor want, NB to suddenly think "OOhh, I know, why don't I start this job again, he must've forgotten all about it :smileytongue: "
Can't find any timeouts anywhere for length of time job is suspended - maybe it's under the 'lets annoy the operator tab' :smileyvery-happy:
NB 6.5.1
Solaris 9 Master/Media
Well that's confirmed it! (But not sure if it's a FEATURE or a BUG)
Andy Welburn wrote:All I can put it down to is the "Clean Up" option "Move backup job from incomplete state to done state". This was set to the default 3 hours and the suspended job 'failed' after 3hours 1minute & 0seconds.
Anyway, have changed this setting to 6 hours so we'll see next time (or sooner if that setting causes me more problems in the meantime).
A job was suspended this morning & 6 hours later it 'failed' & restarted automatically !!!!
(Actually I suspended a child process in a multi-streamed job - for info yesterday it wasn't a multi-streamed job. The other children & parent processes continued running. When all the other child processes finished the parent process then went into a suspended state & then nothing. I presume at this stage I would've had to have waited a further 6 hours to elapse before anything happened. Being impatient, I cancelled the suspended parent process at which point new parent & child processes started.)
So BEWARE - if you suspend a job, check the time in the Master servers "Clean Up" option "Move backup job from incomplete state to done state" as your job will restart after this period has elapsed.