Cluster Server 7.4.1 Implementation Guide for Microsoft Exchange 2010 - Windows
- Introducing the VCS agents for Exchange and NetApp
- Installing the product and configuring a VCS cluster
- Installing Microsoft Exchange Server 2010
- Configuring the Exchange database service group
- Creating the Exchange database service group
- About verifying the service group configuration
- About modifying the Exchange database service group configuration
- Making a standalone Exchange server highly available
- Deploying Disaster Recovery for Exchange Server
- Removing the software components
- Troubleshooting
- Appendix A. Resource type definitions
- Appendix B. Sample Configurations
Setting up disaster recovery configuration
The following table lists the tasks for disaster recovery configuration for Exchange Server.
Table: Tasks for configuring a disaster recovery setup
Tasks | Description |
---|---|
Set up the primary site | Make sure you have completed the following tasks at the primary site:
|
Set up the secondary site | Perform the following tasks to set up the cluster on the secondary site:
|
Back up and restore the Exchange data files | A DR installation of Microsoft Exchange does not create Exchange data files. Therefore, after installing Exchange on the secondary site, you must back up the Exchange volumes or LUNs on the primary site and then restore it on the secondary site. Make sure you restore the data at the same path at the secondary site as on the primary site. Note: Perform this step only once at the secondary site. Complete the following tasks:
|
Configure the Exchange service group at the secondary site | Configuring the Exchange service group involves creating an Exchange service group and defining the attribute values for its resources. See About configuring the Exchange service group. Note the following before configuring the Exchange service group:
|
Configure replication using NetApp SnapMirror | You can replicate Exchange data by establishing a SnapMirror relationship between the filers at the primary and secondary sites. Before configuring replication, make sure the service group is offline at the secondary site. SnapMirror replicates snapshots taken on a filer and applies them to a remote filer over a wide area network; these snapshots can be used by the target host to provide rapid failover in case of a disaster. You can transfer the initial base snapshot image from the primary to secondary via tape, and then set up incremental SnapMirror updates to the destination filer. Refer to NetApp documentation for more information. |
Configure NetApp SnapMirror resources at the primary site | Configure NetAppSnapMirror resources at the primary site to monitor data replication from the primary site to the secondary site. See Configure NetAppSnapMirror resources at the primary site. |
Link clusters at primary and secondary sites | Once all the setup tasks are completed at the primary and secondary sites, you must link the clusters at both the sites. The VCS Java Console provides a wizard to create global cluster by linking standalone clusters. For instructions, review the chapter on Administering Global Clusters from Cluster Manager (Java Console). See the Cluster Server Administrator's Guide. |
Make the Exchange service group global | After linking the clusters at the primary and secondary sites, use the Global Group Configuration Wizard from the Java Console to convert the Exchange service group from a local service group to a global service group. This will enable the Exchange service group to fail over across clusters. For instructions, review the chapter on Administering Global Clusters from Cluster Manager (Java Console). See the Cluster Server Administrator's Guide. |