cancel
Showing results for 
Search instead for 
Did you mean: 

"Time Window for each run day", doesn't always work?

562816057
Not applicable
I had a job defined that only was able to run in a very limited time window because of the need to lock files. I gave it a time window of 1:00am to 1:15am Saturdays.

A previous scheduled job had locked up the job queue (waiting for a tape) and all scheduled jobs were pending for days.

After clearing the locked job, the remaining jobs began to run, including the Saturday job, although they were out of their time Windows.

I'm in a lot of trouble because the Saturday job that had the limited time window ran and corrupted a critical database.

How can this be explained?
5 REPLIES 5

Steven_Cannon
Level 3
I've had a similar thing happen in v9.1. The jobs run outside of their time window when they get a chance and I can't see any way of stopping them.

Ken_Putnam
Level 6
Those other jobs had actually "started" at their assigned times, they were just waiting for a response to the hung job.

Had you also selected the Automatic Cancellation option? see page 375 of the Admin Guide



6. Click Enable automatic cancellation, and then type the number of hours or minutes in the Cancel job if not completed within option.

Steven_Cannon
Level 3
I've stopped trying to stop the jobs from coming up as 'Out of Time Window' as I can't see how to. What I do instead is....

Make sure there isn't a tape in the drive.
Run the job that is 'Out of Time Window'.
You are then prompted to insert Media.
Cancel the job.
Hey presto - the schedule is back to normal.

Sorted!

Chaitanya_Khurj
Level 6
Hello there,

Here are a few technotes which might give you a better insight as regards to what the problem could be !

How to configure a job to run within a specified time frame

http://support.veritas.com/docs/269240

What to check when Backup Exec for Windows Servers jobs are not running according to schedule

http://support.veritas.com/docs/192098

Due to time changes related to daylight savings time VERITAS Backup Exec (tm) 9.x for Windows Servers jobs will run one hour before or one hour after the previously defined schedule

http://support.veritas.com/docs/267203

When schedule jobs run, they go immediately into the "Not in Time Window" status
http://support.veritas.com/docs/264665

Hopefully this should resolve your issue.

NOTE : If we do not receive your intimation within two business days, this post would be "assumed answered" and archived

Madhuri_Shenoy
Level 6
As per our previous reply, marking the case as "assumed answered" and moving it to "answered questions" pool.