Storage Foundation and High Availability Solutions 7.4 HA and DR Solutions Guide for Microsoft Exchange 2010 - Windows
- Section I. Introduction and Concepts
- Introducing Storage Foundation and High Availability Solutions for Microsoft Exchange Server
- How VCS monitors storage components
- Introducing the VCS agent for Exchange 2010
- Introducing Storage Foundation and High Availability Solutions for Microsoft Exchange Server
- Section II. Configuration Workflows
- Configuring high availability for Exchange Server with InfoScale Enterprise
- Reviewing the HA configuration
- Reviewing a standalone Exchange Server configuration
- Reviewing the Replicated Data Cluster configuration
- Reviewing the disaster recovery configuration
- Disaster recovery configuration
- Notes and recommendations for cluster and application configuration
- Configuring disk groups and volumes for Exchange Server
- About managing disk groups and volumes
- Configuring the cluster using the Cluster Configuration Wizard
- Using the Solutions Configuration Center
- Configuring high availability for Exchange Server with InfoScale Enterprise
- Section III. Deployment
- Installing Exchange Server 2010
- Configuring Exchange Server for failover
- Configuring the service group in a non-shared storage environment
- Configuring campus clusters for Exchange Server
- Configuring Replicated Data Clusters for Exchange Server
- Setting up the Replicated Data Sets (RDS)
- Configuring a RVG service group for replication
- Configuring the resources in the RVG service group for RDC replication
- Configuring the RVG Primary resources
- Adding the nodes from the secondary zone to the RDC
- Verifying the RDC configuration
- Deploying disaster recovery for Exchange Server
- Reviewing the disaster recovery configuration
- Setting up your replication environment
- Configuring replication and global clustering
- Configuring the global cluster option for wide-area failover
- Possible task after creating the DR environment: Adding a new failover node to a Volume Replicator environment
- Testing fault readiness by running a fire drill
- About the Fire Drill Wizard
- About post-fire drill scripts
- Prerequisites for a fire drill
- Preparing the fire drill configuration
- Running a fire drill
- Deleting the fire drill configuration
- Section IV. Reference
- Appendix A. Using Veritas AppProtect for vSphere
- Appendix B. Troubleshooting
- Appendix A. Using Veritas AppProtect for vSphere
Creating a parallel environment in the secondary zone
After setting up a SFW HA environment in the primary zone, you set up a parallel environment in the secondary zone (zone 1).
Before you begin to configure the secondary zone, do the following:
Offline the following resources in the Exchange service group in the primary zone:
Exchange Server resource
Exchange virtual server name resource
Exchange virtual IP resource
The remaining resources should be online, including the storage resources.
In VEA, make sure to remove all the drive letters from the configured volumes, to avoid conflicts when configuring the zones.
Then complete the following tasks to configure the secondary zone, using the guidelines shown:
Installing the Veritas InfoScale product.
For more information, see the Veritas InfoScale Installation and Upgrade Guide.
See Configuring disk groups and volumes for Exchange Server.
During the creation of disk groups and volumes for the secondary zone, make sure the following is exactly the same as the cluster at the primary zone:
Disk group name
Volume sizes
Volume names
Drive letters
Installing Exchange Server on additional nodes
Follow the pre-installation, installation, and post-installation steps in the section on installing on additional nodes to install Exchange on all nodes in the secondary zone.
Note:
After you install Exchange on the nodes in the secondary zone, make sure to use VEA to remove all the drive letters from the configured volumes to avoid conflicts during the configuration of the zones.
Adding a system to the existing cluster
You do not create another cluster in the secondary zone. Instead you add the systems to the existing cluster.
You do not create another Exchange Server service group in the secondary zone. You continue with the remaining Volume Replicator configuration tasks, during which the secondary zone nodes will be added to the Exchange Server service group.