Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
backup window closed error 196 ??? 2
- Thread starter pctekk
- Start date
-
1
- #2
- Thread starter
- #3
just have all jobs fail w/
"client backup was not attempted because backup window closed(196)"
i have several policies each w/ different times, run every nite
6pm - 3am window
mid - 3am window
11pm - 4am window
9pm - 1am window
etc..........
so they pretty much all vary in times
"client backup was not attempted because backup window closed(196)"
i have several policies each w/ different times, run every nite
6pm - 3am window
mid - 3am window
11pm - 4am window
9pm - 1am window
etc..........
so they pretty much all vary in times
- Thread starter
- #5
OK then that means the jobs get queued but never go active.
Eventually the window closes before they even have a chance to go attempt a start.
I suggest checking the VERITAS "Knowledge Base Search" for
job stays queued
Bob Stump
Incorrigible punster -- Do not incorrige
Eventually the window closes before they even have a chance to go attempt a start.
I suggest checking the VERITAS "Knowledge Base Search" for
job stays queued
Bob Stump
Incorrigible punster -- Do not incorrige
-
1
- #7
Job get put in to the queue when the window opens, they then sit there untill a resorce becomes avalible to run them. If the resorces are busy for example rerunning failed jobs, slow throughput or down drive, then the jobs in the queue may never get a chance to use the resores before the window closes. In that case you will get a 196. Look at what is happening to stop the jobs starting. Also check the policy settings to ensure that the jobs are getting a fair shot at running.
If you have a window of 3 hours and a frequency of 1 day then the job will go into the queue 24 hours after the last time it ran. So if the last time it ran it only managed to start 1 minute befoe the end of the queue then next's days job will go into the queue 1 minute from the end of thw window. But the scheduler only checks for jobs to submit every 5 to 10 minutes (dependant on your settings) so you could miss your slot.
If you have a window of 3 hours and a frequency of 1 day then the job will go into the queue 24 hours after the last time it ran. So if the last time it ran it only managed to start 1 minute befoe the end of the queue then next's days job will go into the queue 1 minute from the end of thw window. But the scheduler only checks for jobs to submit every 5 to 10 minutes (dependant on your settings) so you could miss your slot.
- Thread starter
- #8
- Status
Similar threads
- Locked
- Question