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
VCS campus cluster configuration
You can configure a new Storage Foundation and High Availability Solutions environment for your application in a campus cluster configuration. A campus cluster environment provides high availability and disaster recovery that extends beyond local clustering and mirroring at a single site, but is not as complex as SFW HA DR solution with replication.
Veritas recommends using the Solutions Configuration Center as a guide for installing InfoScale Enterprise and configuring SFW HA for your application.
See Workflows in the Solutions Configuration Center.
The following table outlines the high-level tasks to complete each objective for a campus cluster configuration for your application.
Table: Task list: Exchange Server campus cluster configuration
Action | Description |
---|---|
Review the campus cluster configuration |
|
Configure storage hardware and network |
|
Review pre-requisites and install InfoScale Enterprise |
|
Review application-specific requirements | See Notes and recommendations for cluster and application configuration. |
Configure disk groups and volumes for Exchange Server |
See Configuring disk groups and volumes for Exchange Server. |
Configure the VCS cluster |
See Configuring the cluster using the Cluster Configuration Wizard. |
Install and configure Exchange Server |
|
Create Exchange databases on shared storage |
|
Create an Exchange service group |
|
Set the ForceImport attribute of the VMDg resource as per the requirement | If a site failure occurs, set the ForceImport attribute of the VMDg resource to 1 to ensure proper failover See Setting the ForceImport attribute to 1 after a site failure. |