You are here: Workload protection > Application protection > Protecting an Exchange server overview

Protecting an Exchange server

To configure protection for your Exchange servers, you will complete the following steps:

Install Exchange on the source server and apply any Exchange service packs or patches. Use the default installation options for Exchange.
Install Exchange on the target, placing it in the same Exchange organization as the source and verifying that the installation location for the target is the same as the source. Apply any Exchange service packs or patches. Use the default installation options for Exchange with the following considerations:

The target must be a unique installation (that is, two Exchange servers must be available for a protection pair).
Logical drive mapping must be the same on the source and target, and must be assigned prior to running the Application Manager.

To protect your Exchange server, you will complete the following steps:

In the event of a failure, you will need to perform some additional tasks. These tasks are described in Failover, Failback, and Restoration.

Note:

If you need to protect any data that is stored on a non-mailbox server role (for example, SMTP queue data), you will need to configure protection for that data separately. In addition, you may need to manually update the DNS setting for the client access server to point to the target site.
If the source Exchange server has a public store that has a non-MAPI Owning Tree, the folders within this tree may not be updated with current information, thus unavailable to the users.
When NAT or certain VPNs exist between the Application Manager and either the source or target, the Application Manager will be unable to configure protection due to limitations of WMI. Please contact Double-Take Software technical support to obtain instructions for configuring protection manually.