Im having an issue with Backup Exec 9.1 that seems to be new over the last few months. Im not sure if this same issue was present before the 9.0 to 9.1 upgrade.
The issue is that I receive not in time window in the status column when I have two jobs running and the second job is waiting for the first job to complete. The status of the second job will continue to read not in time window until the next day and will begin running at the time specified but a day late rather than queuing and running as soon as the drive is ready after the first backup completes.
Normally, I could schedule two jobs back to back and the second job would queue and then run right after the first job completes. So If I had the first job scheduled for 1 PM and had the second job scheduled for 2 PM the 2 PM job would queue until job 1 completed - even if it was 10 hours later.
Now, if the two schedules overlap, the second job displays a status of not in time window and does not run even after the overlapping first job has completed. Whats even stranger is that the same, second job with a status of not in time window will run the following day (a day late) at the scheduled time. Its like an error handling rule is retrying the job again the next day.
Ill need to check on the error handling rule but that still does not explain why the second job is not queuing properly and not running as soon as the first job completes. Any help on this would be greatly appreciated.