I turned up to work this morning to find the following error message on my two BE servers - both use SSO to access a common tape library, and both happen to kick off a B2S job at 19:00. Normally.
"The job was scheduled to run, but the availablility window closed before the job could start. There may not have been any destination devices available during the window, or the job may have been submitted to run when the window was closed."
And the job summary Window had:-
Original Start time : 31 March 2008 20:00:00
Job Started : 31 March 2008 19:00:00
Now, the jobs are both scheduled to start at 19:00, and none of the other criteria for the error are met. The jobs were fine on the Saturday before, and have been running happily for months.
Two other jobs on the 31st, scheduled to start at 22:00 were unaffected.
In the wee hours of Sunday morning of the 30th, the clocks went from GMT to BST. Both the affected jobs were running a Duplicate to Tape from the same policy as the errored job above. This appears to be the only link, that I can see. There's nothing untoward in the event logs.
I'm puzzled - bug in the scheduler?
