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
Sample disk group and volume configuration for Exchange 2010
When configuring disk groups and volumes for Exchange 2010 mailbox databases, you need to consider whether you want each mailbox database to be able to fail over independently, or whether you want to set up service groups that include multiple databases that will fail over as a group.
To enable single mailbox database failover, you must create an independent disk group for each database, and the disk group must contain the database volume and log volume for that database only. Then create a service group for that one database.
Each disk group must contain both the database volume and the log volume to ensure successful failover of the database.
If you choose to include multiple databases in the same disk group, all the included databases will be part of the same service group and will fail over together to another system in the cluster.
The following would be an example configuration for the single database failover scenario in which there are two Exchange mailbox databases:
SG1_DG is a disk group that contains the following:
SG1_DB1 is the volume for Exchange mailbox database 1.
DB1_LOG is the volume that contains the transaction log for the database.
SG2_DG is a separate disk group that contains the following:
SG1_DB2 is the volume for Exchange mailbox database 2.
DB2_LOG is the volume that contains the transaction log for the database.