Scheduling multiple Backups Overnight - a new idea

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 14
Comments: 5

I have Drives C, D, E, F, and G

It is tricky to get the scheduling arranged. I want to do nightly Incrementals - where the first Backup is always a Full and then you set how many Incrementals ro run before the entire set is deleted and the sqequence starts over with a Full.

I set all drives to backup 14 times - then a new set is started and the old set deleted.
I set them to run at 2 AM, 3 AM, etc (1 hour apart). BUT when it reaches the 15th night a FULL backup is executed and this will take more than 1 hour.

If the 2 AM backup does not complete until 3:30 - I do not know if the 3 am backup will start at 3 am and run concurrently with the still executing 2 am backup, or if it will wait for the 2 am backup to complete (i.e. it would be placed in a queue). I assume that it waits in a queue but I am not sure.

If it waits and the 3 am, 4 am, etc backups all end up being placed in a queue . . . why not just set all the backups to run one minute apart - at 2:00 AM, 2:01 AM, 2:02 AM, etc. This way I can be assured they will always run one right after the other and will never "wait" for their time to arrive. The advantage is that they will always finish in the shortest time possible. It will not take from 1 AM to well past 6 am to finsh all backups. So if I wake up at 5 am to do some work, all the backups will have completed since they no longer have to wait one hour in between. Will this 2nd method of scheduling work ?? Or will they all run concurrently (I do not want that).

ls
.

Wed, 09/15/2010 - 16:47
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 14
Comments: 5

I just ran a Test - scheduled E drive to Backup at 1:45 PM and M drive to backup at 1:17 PM.
E drive started backing up and then for M drive it says "Queued".

I then stopped both jobs and edited the Start time to 1:52 PM so they were both set to start at the same time.
When 1:52 came, the first job started running and th secodn job said "Queued"

So you CAN set your jobs to run one right after the other by either separateing the Start times by 1 minute or setting them all to the SAME time. This is a lot better than "guessing" how much time each job will take (I had guessed 1 hour and schedule them to run at 1 am, 2 am, etc).

Wed, 09/15/2010 - 17:54