You are here: Exchange protection > Exchange requirements

Exchange requirements

In addition to the Core Double-Take requirements, you must also meet the following requirements to protect Exchange.

Exchange versions—Double-Take can protect Microsoft Exchange 2003, 2007 or Exchange 2010. Exchange 2010 must have Service Pack 1 or later.
Exchange and network configuration—The following requirements and limitations apply to your Exchange server and network configuration.

All Microsoft best practices should be used for all versions of Exchange.
The version of Exchange on the source and target must be identical.
Windows 2012 is not supported.
Exchange 2010 must be running on a 64-bit server running Windows 2008 SP2 or later or Windows 2008 R2.
Double-Take does not check the edition of Exchange 2007 (Enterprise or Standard). However, it is able to differentiate between service pack levels. If you have Exchange 2007 Enterprise on the source and Exchange 2007 Standard on the target, you will be limited to only failing over the number of databases or storage groups supported by Exchange 2007 Standard. See the Exchange Server 2007 Editions and Client Access Licenses information on the Microsoft website.
For Exchange 2007 and 2010, in a consolidated role environment only the mailbox role is protected. The Hub Transport and Client Access roles are not protected or failed over because they are already installed on the target.
For Exchange 2007 and 2010, replication and failover between a distributed role source configuration to a consolidated role target configuration is permitted as long as the source Mailbox Server role is installed on a standalone server or cluster with the other roles residing on different servers, and the target configuration is a standalone server with the Mailbox, Hub Transport, and Client Access roles installed. In these configurations, Double-Take will not replicate any data associated with the Hub Transport/Client Access data, however, the target Hub Transport/Client Access roles function properly when failing over the source Mailbox role, allowing necessary operations to resume. For Exchange 2010 with DAG (Database Availability Group), replication and failover from a distributed role source configuration must be to a non-DAG distributed role target configuration.
For Exchange 2010 with DAG, the following requirements and limitations also apply.
- A DAG to standalone configuration is the only supported configuration. Multi-site DAGs (DAG to DAG configurations) are not supported.
- All mailbox stores must be replicated to all other members of the DAG.
- During failover, Double-Take will update SPNs, move user mailboxes, and perform Active Directory updates. DNS updates are not made during failover, but can be scripted manually if needed.
Exchange 2003 on a domain controller is not a recommended configuration. However, if you must run Exchange 2003 on a domain controller, review Microsoft Knowledge Base articles 822179, 332097, 305065, 304403, and 875427.
If you are protecting Exchange 2003 and it is running in mixed mode, the first installed Exchange virtual server contains the MTA (Message Transfer Agent) resource that is needed to communicate with versions prior to Exchange 2003. If you do not failover all Exchange virtual servers, then any user who is in a different mail store than the first one may not be able to route mail.
The Exchange program files must be installed in the same location on the source and target.
The drive letter(s) where Exchange stores its data on the source must be the same on the target.
Single-label DNS domain names (those without a suffix such as .com, .corp, .net) are not supported.
In environments where the FIPS security policy is enabled, you must use impersonation, which requires the following.
- The user running the Double-Take Console must have all appropriate rights to update the domain (that is, only impersonation is supported).
- You must manually verify DNS rights by running the DFO utility with the /test parameter.
If you are protecting Exchange 2007 and will only be protecting a subset of the storage groups, the storage groups you are protecting cannot have a hyphen followed by a space in the storage group name. You will either need to change the name of the storage group to remove the hyphen followed by the space, or select all of your storage groups for protection.
Microsoft Server Core is not supported.
The source and target servers must be in the same root forest domain.
In a parent/child domain, at least one domain controller in the child domain must be designated as a global catalog server.
The target server cannot be a domain controller.
Exchange and a domain controller cannot be on the same node of a cluster.
The source and target servers must be part of the same Exchange Administrative Group.
The Exchange configurations on the source and target servers must be identical for the following components: storage groups, location of storage groups (log and data files), log file prefixes, database locations (log and data files), Message Transfer Agent (MTA) location, and queue paths.
Before you attempt to protect your Exchange application, you may want to complete the following tasks to verify that the environment is properly set up.
- With both Exchange servers online, use Active Directory Users and Computers to move an existing user from the source to the target and then back to the original source.
- Verify that you can create a new user on the target.
- To verify connectivity, create an Outlook profile for the new user on a client machine and connect to the target.
- If /domainprep has not been run in an Exchange 2007 environment, users will not be failed over and SPNs will not be updated during failover due to access denied errors. To fix this issue, run setup with the /domainprep parameter in the environment.

Snapshots—You can take and failover to Double-Take snapshots using an Exchange job, however snapshots are not supported if your source and/or target is a cluster. See Core Double-Take requirements for the specific snapshot requirements.

Supported configurations—The following table identifies the supported configurations for an Exchange job.

Configuration		Supported	Not Supported
Source to target configuration	One to one, active/standby	X
	One to one, active/active		X
	Many to one		X
	One to many		X
	Chained		X
	Single server		X
Server configuration¹	Standalone to standalone	X
	Standalone to cluster		X
	Cluster to standalone	X
	Cluster to cluster	X
	Cluster Shared Volumes (CSV) guest level	X
	Cluster Shared Volumes (CSV) host level		X
Upgrade configuration²	Upgrade 5.3 Double-Take Application Manager job to 7.0 Double-Take Console Exchange job		X
Upgrade configuration²	Upgrade 6.0 Exchange job to 7.0 Exchange job	X
Version 7.0 console³	Version 7.0 console can create job for 5.3 source and 5.3 target		X
	Version 7.0 console can create job for 6.0 source and 6.0 target	X
	Version 7.0 console can create job for 7.0 source and 7.0 target	X

When using a supported cluster configuration, the following limitations also apply.
- If you are using Exchange 2007, only the mailbox role is protected.
- Exchange and the domain controller cannot be on the same node in the cluster.
- Exchange must be installed in a unique group, not in the cluster group.
For an upgrade configuration that is not supported, you will have to delete the existing job before the upgrade and create a new job after the upgrade.
Newer job options available in the version 7.0 console will not be functional when creating jobs for servers running version 6.0.