Back in January, I wrote a post about the possibility of job-centric options coming back to the Backup Exec product line. My inside sources had told me October initially, then later February and now I guess later still. For more details on the job-centric versus server-centric debate please see the previous post.
One thing I wanted to add to the argument against, server-centric backups in 2012, which dawned on me recently, was the use of an autoloader or robotic tape library with Backup Exec 2012.
Going back to the previous version of Backup Exec, 2010 and earlier, and using my 10 servers example from the last post, most people are aware that the average robotic arm takes 2-3 minutes to move a tape from a slot and into the drive. The same can be said on the back end of the job where the tape is removed from the drive and moved back into the slot.
Under the job-centric philosophy of 2010, one job that backs up 10 servers, only had this movement happen twice. Once at the beginning of the job and once and the end of the job (unless your job spanned multiple tapes – for the sake of this example lets assume you can fit it all onto one tape).
Under the Backup Exec 2012 server-centric philosophy, those ten servers are now ten individual jobs. That tape now moves twice for each server/job. So, the same backup now has 20 tape movements in a robotic library/autoloader as opposed to 2.
The problem here is the amount of time that adds to the backup window you used to have in 2010. In 2010 the average robotic-libraries tape operations were likely 4-6 minutes. Now using our 10 server example in 2012, the tape operations have been multiplied ten-fold, so your tape operations have increased to 36-54 minutes. Adding 54 minutes to your backup window may not be desirable.
Hopefully, we will see job-centric return soon as an option.