BE2012 Staggered jobs dont start in sequence
Created: 12 Feb 2014 • Updated: 12 Feb 2014 | 2 comments
This issue has been solved. See solution.
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.