Microsoft Exchange Server

Production End

1. Ensure that the name of the Exchange email database at the production end meets naming requirements.

   The database name can contain only letters, digits, and special characters including _ - @ # $ *.

2. Check the VSS service status of the application host where the Exchange email database at the production end resides.

   eReplication Agent uses the VSS service to ensure consistency between Exchange applications. Therefore, the VSS service must be enabled when eReplication Agent is working.

3. Check Exchange data files at the production end.
   • Data files and log files in databases used by Exchange must be stored on storage array LUNs.
   • The Exchange 2013 email database cannot include public folders.

4. The protected databases must be in the mount state to ensure consistency.

DR End

1. Check the Exchange environment at the DR end.
   

   If the Exchange 2007 environments at the DR end and production end are not the same, the user should deal with it to make sure that the DR end and production end have the same Exchange environments.

   1. Check whether the operating system and its edition run by Exchange 2007, Exchange 2010, or Exchange 2013 are the same as that at the production end.
   2. Check whether the versions of Exchange 2007, Exchange 2010, or Exchange 2013 are the same as that at the production end.
   3. Check whether names of storage groups used by Exchange 2007 are the same as that at the production end.
   4. Check whether the locations that data files and log files in databases used by Exchange 2007 are stored are the same as that at the production end.
   5. Check whether the organization name of the Exchange 2010 mailbox database at the DR site is the same as that at the production end.

2. Before performing a DR test or recovery, you need to disable the Exchange service at the DR end for Exchange 2007 and enable the Exchange service at the DR end for Exchange 2010 and Exchange 2013.

Storage End

• Check the storage environments of the production end and the DR end.

  Check the remote replication between the production end and the DR end. Before using remote replication to protect objects at the production end, ensure that the remote replication is normal between the production end and the DR end.

• Check the storage environments of the DR end.
  1. Delete the LUNs mapped to the DR host or test host at the DR end and ensure that the corresponding drive letters are not occupied by other LUNs.
  2. After setting up an application environment on the DR end, delete the mapping between the host and the storage LUNs or volumes that store the data files and log files of the application.
  3. If the DR storage is the S5000 series or T series V1, map the initiator of the physical DR host to the logical host of the DR storage. In a cluster, add the logical host to the host group.
  4. If the storage is T series V2R2 or later or 18000 series, the storage support automatically add host and storage mapping function. If the connection between the storage device and the host initiator is normal, the hosts, host groups, LUN mappings, and mapping view will be created in the storage device automatically.
  5. If the DR storage is T series V2 or later or 18000 series, the DR host can belong to only one host group that belongs to only one mapping view. The remote replication secondary LUN that corresponds to the storage LUN used by the protected applications can belong to only one LUN group, and the LUN group must belong to the same mapping view as the host group.