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
Prerequisites for configuring cluster disk groups and volumes
Before you create a disk group (cluster disk group or dynamic disk group), consider the following items:
The type of volume configurations that are required
The number of volumes or LUNs required for the disk group
The implications of backup and restore operations on the disk group setup
The size of databases and logs that depend on the traffic load
The disk groups and number of disks on each site
Types of volumes required and location of the plex of each volume in the storage array
Complete the following tasks before you create the cluster disk group and volumes for Exchange:
Determine the layout or configuration for each volume and the total number of disks needed.
Determine the initial size necessary for the volumes. You may increase the volume size at a later time using the Expand Volume command but you can not decrease the size.
If using shared storage, verify that the disks you plan to include in the cluster disk group are shared and are available from all nodes. If new disks are installed, you must rescan, and if necessary, use the Write Signature command in order to identify the disks to the operating system.
For Exchange 2010, there are additional requirements if you want to configure the disk group and volumes so that each Exchange database can fail over independently of any others.
See Sample disk group and volume configuration for Exchange 2010.
For more information on disk group and volume requirements for specific configurations, see the following topics:
For service groups with many disk groups, you may want to implement the fast failover feature. Read the following topic: See Considerations for a fast failover configuration.
If the existing databases and logs are already on shared storage, read the following topic: See Considerations for converting existing shared storage to cluster disk groups and volumes.
For more information on disk groups and volumes for campus clusters, read the following topic: See Considerations when creating disks and volumes for campus clusters.
For a Replicated Data Cluster (RDC) configuration or a disaster recovery (DR) configuration using Volume Replicator (Volume Replicator), read the following topic: See Considerations for volumes for a Volume Replicator configuration.