coldnature
IS-IT--Management
Basically, jobs scheduled 10 minutes apart that take longer than 10 minutes to run, do not run in order!
Here are the details of the problem I'm having, hopefully it doesn't get too confusing...
We run multiple backup jobs each night. Thursday nights are as follows:
Exchange Full Backup - 6PM
Exchange Incremental - 11:00
Accounting Full (Only 600 megs) - 11:10
File Server Incremental - 11:20
File Server Full Backup - 11:30
We are using a PV132T and the reason the backup jobs are split up like this is to store different information on different tapes. I've scheduled the last four backups 10 minutes apart, thinking they will run in order, knowing they each take more than 10 minutes. I just want that full file server backup to start as soon as possible (it takes all night).
Here is what I find every Friday morning: Exchange full starts at 6, ends at 11:34. Somehow, the Full File backup and the Exchange Incremental indicate start times of 11:34. The exchange runs first, completes in 40 minutes, then the File ACTUALLY starts and runs all night. After that, the other two jobs that were SUPPOSED to run first, run.
It doesnt seem to be handling the job start time well if another job is already running. I know I can adjust the start times based upon how long the jobs really take, but that would require constant adjustment since the stores grow regularly.
Has anyone else experienced this?
Thanks
Here are the details of the problem I'm having, hopefully it doesn't get too confusing...
We run multiple backup jobs each night. Thursday nights are as follows:
Exchange Full Backup - 6PM
Exchange Incremental - 11:00
Accounting Full (Only 600 megs) - 11:10
File Server Incremental - 11:20
File Server Full Backup - 11:30
We are using a PV132T and the reason the backup jobs are split up like this is to store different information on different tapes. I've scheduled the last four backups 10 minutes apart, thinking they will run in order, knowing they each take more than 10 minutes. I just want that full file server backup to start as soon as possible (it takes all night).
Here is what I find every Friday morning: Exchange full starts at 6, ends at 11:34. Somehow, the Full File backup and the Exchange Incremental indicate start times of 11:34. The exchange runs first, completes in 40 minutes, then the File ACTUALLY starts and runs all night. After that, the other two jobs that were SUPPOSED to run first, run.
It doesnt seem to be handling the job start time well if another job is already running. I know I can adjust the start times based upon how long the jobs really take, but that would require constant adjustment since the stores grow regularly.
Has anyone else experienced this?
Thanks