Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


Return to article

Backup and Restore Strategies for Exchange Server
 

Let’s talk about backup and restore for Exchange Server. I am curious about common practices among Exchange Server deployments. What are you doing to ensure your Exchange Server data is safe and sound?

Microsoft provides three main types of backup methods (four, if you count the Copy option), and many strategies exist for combining these methods depending on your goals and sensitivity to data loss. The three types of commonly used backup methods are full, incremental, and differential. Traditional thinking tells us that a full backup followed by daily incremental backups is the best course of action. The advantage of this strategy is that backup time is minimal for each daily incremental backup, because only the transaction logs (which are 5MB each) are copied to tape. However, when you have to restore with this strategy, you must restore the initial full backup tape plus every daily incremental tape. If your Exchange Server crashed Friday and you made your full backup Saturday, you would need the full backup tape plus five more tapes from the backups from Sunday through Thursday. Although completely legitimate, this strategy does have some drawbacks.

Another strategy, which doesn't require every daily backup tape since the full backup in the strategy above, would be to combine a full backup with daily differential backups. For Exchange Server, the differential backup simply copies all the transaction logs since the last full backup. Using this strategy for Exchange Server alleviates the need to pack so many tapes. When you perform a restore, you need only the full backup and the latest differential backup tapes. The disadvantage is that each daily differential backup takes longer as the week progresses, depending on the amount of transaction logs that accumulate (depending on server load) on the Exchange server.

Another strategy is the daily full backup option, which more and more Exchange deployments are using. I most often recommend this strategy to organizations I interact with. The daily full backup option is great when you want to recover an Exchange server because you only need one tape from the previous day’s full backup. The downside, however, is that a daily full backup takes more time to perform. When faced with potential loss of mission-critical messaging data, many organizations are more than willing to endure the inconvenience that daily full backups bring.

Whatever your current strategy, it's important that you consider each of the above options and how they fit into your environment. In fact, you might consider additional variants such as a daily full backup combined with a mid-day differential backup for even more data security. Also, check with disaster recovery vendors who support Microsoft Exchange Server (e.g., Computer Associates, Seagate/Veritas, Legato, and UltraBac). The strategy and vendor you select are the most important steps to ensuring disaster tolerance for your Exchange Server deployment.







Reader Comments

This sounds like a discussion of how to backup a file server. As a Network Administrator responsible for managing Exchange, I am much more interested in the merits of on-line versus off-line backups. On-line backups sound appealing, but I have always had diffuculty getting 3rd party programs (like ArcserveIT etc.) to perform a sucessful on-line restore.

Kenneth Henry -August 14, 1999

I perform full online daily backups using the nt backup program. Having lost the Exchange Server once and spending 4 days trying to recover. I am not concerned about the effort to backup, I am primarily cocerned with timely recovery.

John Leone -August 16, 1999

As a former network administrator at a pharmaceutical company, I used to perform online backups of Exchange Server's DS and IS and of the C:\WINNT + registry, all nightly. I combined this with a one-time full backup of the C: drive each time I was installing new software (I used the other drives for Exchange's data and logs and for a second pagefile). With this strategy I was expecting to recover up to the night before the disaster would come. However, I was missing an SQL-like way to backup the logs and replay them after the IS's or DS's restore. Does such a method exist ? What directories should I backup ? Would it work with circular logging ?

Alfonso Piñol -August 17, 1999

I perform a daily full backup of my exchange box because the information is very critical but recently I had 1 user lose his data and wanted to restore just 1 mail box... I did it but it wasn't easy... Required building another exchange box and importing the one mail box to my production server... Any tips for if this happens again... Yes the user deleted all his mail and yes he was the VP of the company.

Vern Bastable -August 17, 1999

Very nice article. I use a full backup method on my servers. In the long run it will save on confusion of multiple tapes, as well as ime in a recovery.

Ralph Browning -August 17, 1999

Nice to see similar solutions to my own. I perform a nightly full backup to a remote tape autoloader, I have no bandwidth issues between these two locations. Very happy with the results.

Thomas Wrobel -September 20, 1999
Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement