Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Multiple Servers to disk to tape

Created: 07 Jan 2013 • Updated: 20 May 2013 | 4 comments
This issue has been solved. See solution.

Hi,

I have searched for an answer to this but have yet to find one that satisfies our requirements. I preface this with the fact that I am fairly new to backup exec and am trying to learn as much about it (and best practices) as I can.

I have a small multi-server, multi domain windows environment. Some physical and some virtual. Our backups take place weekday differential and weekend full backup. There are a number of SBS servers (and therefore exchange information stores, Sharepoint, etc). We back up to an LTO3 Tape library at present using backup exec 2010 r3.

Our issue is that some of our backups are taking a long time to complete and therefore our backup window is starting to fill. The tape library, however, is no where near capacity and rarely reaches the maximum write speed for the device.

In order to alleviate this I have been contemplating having all (or most) of the servers back up to either a single or (ideally)multiple backup to disk folder(s) and then duplicate this to tape outside of the backup window. Therefore utilising the available capacity on the tape drive, improving visibility of successful/failed components of the jobs, improving ease of adding/removing backup jobs and making full use of the available bandwidth.

My problem is that from what i have read I need to use a policy to achieve this. However, When I create a policy (using multiple selection lists, etc) I get multiple backup to disk jobs and then multiple duplicate to tape jobs. Which would result in tape device availability nightmares and an unwieldy job monitor window,

 

Any help in this matter would be greatly appreciated.

Comments 4 CommentsJump to latest comment

Kiran Bandi's picture

When you combine a policy with two templates (one backup and one duplicate) with two selection lists, four jobs will be created. There is no other way around.

what i have read I need to use a policy to achieve this

If you want to create some kind of relation between your jobs, using a policy is the easy and best way of doing it. For example run duplictae to tape job immediately after completing backup to disk.

As you said you want to run Duplicate to tape out of backup window, i presume you have a specific schedule in mind for running duplicate to tape jobs. If so, you can accomplish that by using standalone jobs also.

Refer to this TN about duplicating backup data without using policies: http://www.symantec.com/docs/TECH24544

SOLUTION
Balthaer's picture

Hi Kiran,

Thank you for the quick reply. My apologies for the delayed response - have been out on site.

I will try the instructions in the TN. Would I still be able to restore directly from tape or would it have to be a multi-stage restore?

In the instance of multiple servers would it be better to use multiple backup to disk folders or a single folder, one for each server? My preference is to use a single folder with multiple concurrent jobs for ease of management.

As an aside, I had read somewhere about best practice is to backup exchange as a separate job. Is there any particular reason for this?

Kiran Bandi's picture

Restore can be done directly from duplicate copy i.e tape also...

You can target all you jobs at a single B2D folder, no need of seperate B2D folders for each server.

It is recommended to keep any database backups from file system backups. One reason which comes into my mind is because VSS/VSP (under Advanced Open File) needs to be enabled in file system backups to backup opened files.

pkh's picture

Would I still be able to restore directly from tape or would it have to be a multi-stage restore?

You would be able to restore directly from the tape backup sets.  However, if it is a GRT restore, e.g. Exchange, then th backup set would be staged to disk first before the actual restore begins, so if you have a copy of the backup on disk, it would be better to do a GRT restore from this, rather than from tape.

I had read somewhere about best practice is to backup exchange as a separate job. Is there any particular reason for this?

As previously advised, you need to turn on AOFO to backup opened files.  However AOFO needs to be off when you backup databases like Exchange or SQL databases, so you would need at least 2 jobs, one with AOFO on for file backups and one with AOFO offf for database backups.