BE2012 Staggered jobs dont start in sequence

[djr357]

Backing up 6 servers with 6 staggered jobs so they all start in sequence after eachother regardless of what time they actually get done.

Server 1 - 11:00 PM - B2T - backed up 1st

Server 2 - 11:10 PM - B2T - backed up 2nd

Server 3 - 11:20 PM - B2T - backup up 3rd

server 4 - 11:30 PM - B2T - backed up 5th

server 5 - 11:55 PM - B2D - backed up 4th

server 6 - 11:40 PM - B2T - Backed up 6th

Server 5 - scheduled after the first disk backup ends - D2T - backed up last - this is the correct spot

Why did server 5 B2D job hop over the 11:30 and 11:40 slated jobs? You can also see that after the B2D job finished, the D2T job did not fire, instead, server 4 B2T fired and then server 6 fired THEN the Duplicate job went. I would like Server 5s jobs to go last since that will be the last thing on the tape and if there is no room, the job can terminate. All the other servers info I would like to be on the tape since they are not going to disk first.

[pkh · Accepted solution]

The B2D job will start first because it does not have to wait for the tape drive. Server 4 and 6 jobs are in the queue for the tape drive first

[djr357]

Server 1 - 11:00pm to 11:25pm - Tape

Server 2 - 11:25pm to 11:48pm - Tape

Server 3 - 11:48pm to 12:14am - Tape

Server 4 - 12:14am to 8:08am - Tape

Server 5 - 11:55pm to 5:15am - Disk

Server 6 - 8:08am to 10:35am - Tape

Server 5 - 10:35am to currently going on - Tape

yeah its a lot easier to list it out as it happened! :)

I will reschedule accordingly (dont need ti backing up through the day). It does look like it is doing what it needs to do though. Didnt know it could do two things at once (B2D and B2T) but why couldnt it.... thanks as always!