Please Advise: Exchange backup. Am I missing anything? 1

[eod]

We have backup exec 8.6 running on a NT4 server. One of my main concerns is how we backup out Exchange 5.5 server and being able to recover it in case of a disaster.

Currently we run the Exchange Agent for backup exec. So when my exchange backup job runs it backs up:

The Microsoft Exchange Directory
Microsoft Exchange Information Store

Is there anything else I should include in this backup job? Or is the exchange agent smart enough to grab everything I need in case of disaster.

 

[Guest_imported]

have a backup of ur registry too. that is enuf.

 

[Alshrim]

You must have at least one full back up of the Directory Store - and a backup of the SAM ..(in case of the "Sprinklers go off and render your domain useless&quot. This is a prudent measure for a full desaster recovery plan.

I'll be writing a full paper on what is needed - and I will post it here when I am finished.

You will also find it VERY handy to have full documentation on how your exchange server is set up (paths to logfiles, databases, mta files). Know what agents and connectors are installed on your Exchange server.

If this machine is to ever become unrecoverable, and you are stuck building a fresh machine for your new exchange server, the NEW server will have to be setup EXACTLY like your original, before your restorations can begin.

If your exchange server IS NOT a DC - and your Domain Controllers are no available (worse case scenario) then you will need a copy of the Domain Controller's Registry - and Account Database (SAM). Without this - you will be unable to recover your Exchange server. The mailboxes depend ALOT on the accounts that own them... so the SAM is essential for backup.

I have actually built a BAckup domain controller, and configured it with an INstall repository with all my exchange installation files, with documentation upon it and will store it offsite. Should things around here blow up - I will have a domain controller with a recent copy of the SAM built right on it -- i'll promote it to a PDC if needs be, and I'll have all I need to build my new exchange server.

That's my two sense.. Hope it was helpful.
I will be posting a FAQ here as soon as my documentation is complete.

 

[eod]

Alshrim,

Wow thanks a lot.. This is some great information. I'd be very interested in following a similar recovery method.

Is there a program that I can run that'll spit all my Exchange settings into a text file or do I need to manually go through and record every setting? I'm going to backup my SAM and DC Registry right now and take it off site.

Thanks.. Your information has been extremely helpful.

 

[Alshrim]

My pleasure.

I use Vertias Backup Exec to do all my backups on the Exchange Server. It is "Exchange Aware" so it does online backups without taking the server down.

When doing this kind of backup - I also use Circular Logging - so once there is a full backup made of the IS and DS - it deletes all the backed up logs and keeps your space usage down.

The settings within the Exchange Server are recorded in the Transaction log files in the DS - and all of the INformation that is stored (email, attachements, calanders, Public info) is recorded in the Transaction logs for the IS ... when you do a Full Online Backup of the Stores, these Transactions logs are backed up by Backup Exec.

If you do an Offline back up - this would require you to shut the services down -- once you shut down the services, all changes made to the information store are committed to the Database at the point of shutdown -- so - all you would really require is to back up the PUB.EDB and PRIV.EDB for the IS. Logs at this stage would not be required - but are a nice to have (you can never be too careful). I have the attitude that when backing up - you almost have to have a paranoid attitude -- if you even have to ask "should I back this up" .. do it! hehehe... You can always delete it later.

 

[Alshrim]

I forgot to answer one thing...

To find out the paths to all your db's and logfile..
Open your Exchange Administrator
Browse to the server itself.
File | Properties

And there is a tab called Database Paths.

Tells ya where everything is.

 

[eod]

WOO!! Man I'm getting all sorts of progress done today. Wonderful! I can sleep a lot easier at night..

Here is an embarassing question.. How do I backup the SAM db on the PDC?

 

[Alshrim]

Allow me to correct myself -- (I always get this freakin' confused)

when doing online backups -- do NOT use Circular logging as long as you have the space... here's from Technet:

Using Circular Logging

Circular logging recycles transaction log files by overwriting logs that have been committed to the database with new transactions. This prevents the continuous buildup of transaction log files and reduces the disk space required to store them (typically less than 100 MB). By default, circular logging is turned on in Microsoft Exchange Server. However, you can use the Advanced property page on the server object to turn off circular logging for the directory and information store.
When developing your backup plan, you should consider the implications of using circular logging. Because circular logging overwrites transaction log files, it reduces your ability to recover data. In most cases, you should turn off circular logging to increase your backup options and your ability to recover data.
With circular logging turned on, you can restore information only up to the last full backup—not to the last transaction. When circular logging is turned on, you can only perform full backups, not incremental or differential backups. This is because Windows NT Backup relies on having complete transaction log files to perform incremental and differential backups of the directory and information store databases.
You may want to keep circular logging turned on for some configurations. For example, you could keep circular logging turned on because your server computer has limited hard disk space or because the server is being used as a news server that contains only noncritical data.
For more information about circular logging, see Microsoft Exchange Server Getting Started.

 

[Alshrim]

the easiest way is to do an RDISK.exe /s ERD

But if you have a huge SAM - NTBackup can do it.

SAM is located in %systemroot%\system32
RDISK actually compresses it, and adds it to your Recovery Disk.

I believe Backup Exec has it build in to get it as well.

When I said I have a BDC offsite - I mean -- I have a full machine as a Backup Domain Controller offsite. As a BDC, it holds an exact copy of the Primary Domain Controller's SAM. When you promote it (if you ever have to), it becomes the Primary Holder of the SAM based on its last sych with the PDC.

If you have one - use a laptop -- easily portable, when major changes are done to your domain - bring in the laptop - synch it with the domain - it will receive all the new Account information from the PDC - and voila - instant backup in less than 15 minutes.

Take it off site.. and in the event of a catastrophe - Promote the laptop to a PDC - and you have a working SAM ready for you - without even having to do a restore.

 

[eod]

Alshrim,

Thank you so much for all this valuable information. Right now I got changes and back ups going all over the place and I feel a lot better about how I am running our exchange server.

 

[Alshrim]

I have submitted my White Paper for review. it should be published soon. I will let you know.

 

[Alshrim]

I guess it's already up.. that was quick.

http://www.tek-tips.com/faqs.cfm?spid=10&sfid=2260&CFID=78826408&CFTOKEN=75045884