Video Screencast Help
Backup and Recovery Community Blog

Best practices for preparing the Exchange Server for backup

Created: 26 Aug 2009 • Updated: 26 Aug 2009
bhupeshsingh's picture
0 0 Votes
Login to vote

Circular logging must be disabled if you want to do the following:

Run incremental and differential backups.

Recover data up to the point of failure.

Run continuous backups of Information Store transaction logs.

Put transaction log files on a separate physical disk from the database. If the disk that contains the database is damaged, the transaction logs are available as a recovery resource.

Set the retention period for deleted items and mailboxes to a length of time that is appropriate for the available disk space. The longer the retention period, the more disk space is required. However, some retention period can prevent you from having to restore a mailbox or database. If possible, configure the Exchange server so that items are not deleted until a full backup is performed.

Make Write Cache unavailable on the SCSI controller. Data corruption can occur if the computer fails before the operation is written to disk.

Monitor the Application, Security, and System logs for any relevant events that may affect Exchange Server functionality.

Allow sufficient disk space for maintenance and recovery procedures. Refer to your Microsoft documentation for details.

Document the Exchange server configuration in detail.

Avoid making the Exchange server a domain controller. You can more easily restore Exchange if you don't have to restore the Active Directory first.

Install the Exchange Server into a domain that has at least two domain controllers. With two domain controllers in a domain, databases on a failed domain controller can be updated with replication.

For Exchange Server 2000/2003, ensure that the latest version of the Esebcli2.dll file is installed. If the Esebcli2.dll file is installed in more than one location, ensure that all locations contain the latest version.