How Can I Do This Better

There must be a better way than what I'm doing. In my opinion what I'm doing is overly complicated, the backups take far too long, and I'm running out of resources. Input on what I could do different to reduce the chaos is much appreciated. 

I have Backup Exec 2014 console on Windows 2008 server with a Tandberg storageloader for DDS1 tapes which hold 720GB each. It backs up 9 Windows 2008 servers. I use the method backup to disk then to tape once a week for keeping something offsite. Of those servers, 2 are backed up in full 5 nights a week, 2 are backed up full once a week and incrementals 4 nights a week, and 5 are backed up in full once a week.  Generally the backup to tape is performed once a week on Sundays but there’s not enough time so I separated the verifications to run on Mondays then take tapes home Monday nights. To get all 9 servers on tape now takes four tapes.

For back to disks I have two Synology NAS for most data (highest priority of course) and four lower end external drives for the rest.

No jobs have dependencies meaning I have to carefully calculate the time it will take to run the backups and schedule accordingly.  I must check my jobs often and adjust to accommodate increases in data. I was hoping the move to version 2014 would help with the backup speeds but it didn’t. Instead the backups to disk are a little slower which adds to the frustration.

Attached is a screenshot of my calendar which shows the crazy complexity of my backup schedule. It’s out of control. When I recently upgraded from version 2012 to 2014 all those jobs had to be recreated. I’ve proposed backup to cloud at least once a week to replace the tapes but it may not happen until next year’s budget.

I wish I could do the backup to tape and verifications in one job that covered all servers.

I wish I could create dependencies between server jobs to recoup the time lost between jobs.  In other words, when server 1’s full backup ends, server 2’s full backup starts.

I don’t like doing incrementals because it will take longer for a full restore. Meaning, I would need to start with restore of the last full backup then restore each incremental backup one a a time until current.  I have two servers with incrementals because I don’t have enough time on the schedule for doing more full backups for those servers. I don’t believe changing from incremental to deduplication will be an improvement.  It might save space and time on the backup side of things but not on the full restore end which matters.

I don’t think I can improve upon the fact I need to get at least one full backup to tape of each server weekly and then to put that weekly full backup to tape.  Maybe it’s time I added a second Backup Exec console, Tandberg storageloaders, and dozens of more tapes so I could run two jobs simultaneously?  

7 Replies

I don't see why you don't

I don't see why you don't want to run incementals for the 2 servers. How often do you expect to have to do a full restore? The extra time taken to restore the four incrementals is a small price to pay for the improvement in backup times you will gain.

You can set the disk storage to limit the number of concurrent write jobs. If you set it to one then you can schedule the backups jobs to all start at pretty much the same time and when one job completes another job will start immediately. Just make sure you have the job timeouts set to a long enough wait time. If you set the write limit to 2 then you can run two jobs at a time. The others will sit in Ready state waiting for a running job to complete.


You can chain your jobs so

You can chain your jobs so that they start one after another. See my article below on how to do so https://www-secure.symantec.com/connect/articles/use-bemcli-chain-jobs

Why don't you just schedule

Why don't you just schedule all your jobs at the same time and let Backup Exec sort it out?

Artegic, this weekend I'll

Artegic, this weekend I'll give that a go with scheduling them together. Full backups to start tonight through tomorrow and tapes to run Sunday into Monday along with their verifications instead of separately. 

I set my Synology NAS settings in BE to allow 2 concurrent backups. Is there anywhere else in BE that I also need to change to permit 2 concurrent backups?   

In the Storage tab, you need

In the Storage tab, you need to right-click on the disk storage defined on your NAS and change the concurrency.  Running 2 concurrent jobs does not mean that the overall time will be reduced.  In fact, it might increase due to resource contention.

For your tape jobs, you might want to do some scheduling especially if you are appending to your tapes.

Is it possible to change the

Is it possible to change the tape drive to LTO instead? The DDS backup speed to very slow.

Sorry, DDS is typo on my

Sorry, DDS is typo on my part.  These are Ultrium LTO4 cartridges. 

Last weekend's run went fairly well. Working out some bugs this morning.