Using Arcserve 11.5 on W2K3 with Ultrium 2 LTO library.
I have a GFS scheme that does daily differentials with Friday Fulls. Backing up 4 NAS boxes plus numerous servers and the odd workstation. I've scheduled 8 jobs which together backup everything needed in approximately 70 hours which just nudges into monday morning. The separate jobs mean that if a job fails, it can be rerun in isolation without running another 70 hour job!
The jobs are scheduled at hourly intervals with the first at 1700 and the last at 2359 and are in a specific order (most critical data first). The daily differential jobs usually take up to about an hour or an hour and a half so sometimes a job is scheduled to start whilst a job is in progress and arcserve logs the fact that the job couldn't start every hour until it is able to begin. On weekdays this isn't a problem. The jobs will run in order in most cases. Usually there is never more than one job waiting to run whilst a job is in progress.
My issue is with the full backups. The first Job takes about 15 hours and after 7 of those have elapsed there are 7 backups waiting to run whilst the first is in progress and this gives me various problems.
1) sometimes, some of the jobs never start all weekend.
2) when the first job finishes the next in the queue is not necessarily the one that runs next and my careful job ordering goes right out of the window.
So my question is:
Faced with multiple jobs that have passed their scheduled start time, in what order will arcserve start the waiting jobs and why will it sometimes give trying to start some jobs altogether?