Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Guidance for setting up initial Backup regime

Updated: 08 Jun 2010 | 2 comments
JulianLancaster's picture
0 0 Votes
Login to vote

Hello,

I have recently been assigned the task of taking care of company-wide backups due to a shuffle in the structure of our company. Unfortunately, this is not an area that I have had a lot of experience in. Our previous system was a very simple series of ntbackup scripts that ran every day and stored data on our SAN. As our company has grown it has become clear that this approach is unreliable and inflexible, so I'm going about setting up a system that uses BE 12.5.

After reading a considerable amount of documentation and looking around online I am still quite confused about a few concepts that are preventing me from implementing a simple backup scheme -- it is essential that I have at least a rudimentary regime in place shortly and I am struggling to get one set up. 

Here is a little information about our network environment:

  • The intended storage space for the backups is a 2TB LUN on our SAN;
  • Our organisation consists for a mixture of virtualised and physical Windows Server 2003 and 2008 machines;
  • Amongst the services that I need to have backed up are Exchange 2007, SQL 2005, ISA 2006 and several SPS (sharepoint services) servers;
  • The servers that are virtualised are using ESX 3.5 (VMWare Infrastructure);

Here is my question:

Is there a good, comprehensive guide to setting up a simple backup regime that I could use to set up an initial, basic backup regime for the machines on our network? Failing that, is there a good place I can start in terms of documentation for setting up series of rotating backups? What I am hoping to have set up to start with is something like this--

  • Daily differential backups of core services running from Mon-Friday every week, with last week's days being overwritten on Monday.
  • A full backup of all data and services taken every Saturday on a 8 week rotation for 8 total backups going back 2 months.

To start with, all of these backups would simply be stored on the SAN. I have a tape library, but currently we do not have licensing options to use it with Symantec. Working on that.

Any advice or help greatly appreciated!

-Julian Lancaster

Comments

CraigV's picture
23
Nov
2009
5 Votes +5
Login to vote

Hi Julian, First thing to

Hi Julian,

First thing to look through is the Backup Exec 12.5 Admin Guide which will give you a better grounding on what it does, and how it does it:

http://seer.entsupport.symantec.com/docs/308400.htm

Next up is to get the Installation Guide:

http://seer.entsupport.symantec.com/docs/308993.htm

Couple of things to be aware of here:

1. BEWS 12.5 ships with a license for 1 drive, be it in an autoloader, library or stand-alone unit. You'll be able to use at least 1 drive in that library, even if it has more installed.
2. With a 2TB LUN, you have more than enough space for your data. I'd use that as a Backup-to-Disk target for your Exchange, files, SQL and SharePoint etc. You will need agent licenses for them in order to back them up though, so you need to look into that.
3. Depending on the size of your VM environment, you can also look into using Backup Exec's (licensed!) capability to backup VMs, and if they're not that big, use the 2TB LUN as the target again.
4. If you can, you can also use the option to first backup-to-disk, and then stream off to tape. That would be something to use in the future if you don't have drive licenses installed currently.

Check out those 2 documents, as they'll give you a good start in the right direction!

Laters!

If you find this is a solution, please mark it as such.

CraigV's picture
07
Dec
2009
0 Votes 0
Login to vote

Hi Julian, Come right here?

Hi Julian,

Come right here?

If you find this is a solution, please mark it as such.