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
Moving mailbox databases to shared storage
Note:
This is applicable if you are planning to configure an existing standalone Exchange Server setup for high availability.
Verify the location where all the existing Exchange mailbox databases and logs reside. If they reside on shared disks that are accessible from all the systems where Exchange is installed, then convert the shared disks to cluster disk groups and volumes.
See Considerations for converting existing shared storage to cluster disk groups and volumes.
If the databases and log files do not reside on shared storage, you must move the databases to the appropriate cluster disk groups and volumes on the shared storage. This ensures proper failover operations in the cluster.
Use the Exchange Management Console to move the mailbox databases and log files to shared storage. Refer to the Microsoft documentation for instructions.
Note:
Do not use the Exchange Setup Wizard for VCS to move Exchange mailbox databases to shared storage. Use the Exchange Management Console.
To move the existing mailbox databases to shared storage
- Verify that you have backed up your existing data.
- Create the disk group and volumes required for the Exchange mailbox databases and log files and ensure that the dynamic cluster disk group is imported and the required volumes mounted on the system where the original database and log files are located on the local drives.
See Viewing the available disk storage.
See Creating a dynamic disk group.
See Adding disks to campus cluster sites.
- Use the Exchange Management Console to move the Exchange mailbox database and log files to the shared storage.
Refer to the Microsoft documentation for instructions.