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
Linking clusters: Adding a remote cluster to a local cluster
This is applicable only if you are setting up DR manually in a non-shared storage environment.
The VCS Cluster Manager (Java Console) provides a wizard to create global clusters by linking standalone clusters or bringing a standalone cluster into an existing global environment.
Note the following uses of the wizard:
If you are creating a global cluster environment for the first time with two standalone clusters, run the wizard from either the cluster on the primary site or the cluster on the secondary site.
If you are adding a standalone cluster to an existing global cluster environment, run the wizard from a cluster already in the global cluster environment.
The following information is required for the Remote Cluster Configuration Wizard in VCS Cluster Manager:
The active host name or IP address of each cluster in the global configuration and of the cluster being added to the configuration.
The user name and password of the administrator for each cluster in the configuration.
The user name and password of the administrator for the cluster being added to the configuration.
Veritas InfoScale products do not support adding a cluster that is already part of a global cluster environment. To merge the clusters of one global cluster environment (for example, cluster A and cluster B) with the clusters of another global environment (for example, cluster C and cluster D), separate cluster C and cluster D into standalone clusters and add them one by one to the environment containing cluster A and cluster B.
To add a remote cluster in Cluster Explorer
- From Cluster Explorer, click Edit > Add/Delete Remote Cluster.
or
From the Cluster Explorer configuration tree, right-click the cluster name, and click Add/Delete Remote Cluster.
- Review the required information for the Remote Cluster Configuration Wizard and then click Next.
- In the Wizard Options panel, click Add Cluster, then click Next.
- In the New Cluster Details panel, enter the details of the new cluster.
If the cluster is not running in secure mode, specify the following:
Enter the host name of a cluster system, an IP address of a cluster system, or the IP address of the cluster that will join the global environment.
If necessary, change the default port number.
Enter the user name and the password.
Click Next.
If the cluster is running in secure mode, specify the following:
Enter the host name of a cluster system, an IP address of a cluster system, or the IP address of the cluster that will join the global environment.
Verify the port number.
Choose to connect to the remote cluster with the credentials used for the current cluster connection, or enter new credentials, including the user name, password, and the domain.
If you connected to the remote cluster earlier through the wizard, you can use the credentials from the previous connection.
Click Next.
- Click Finish.
After running the wizard, the configurations on all the relevant clusters are in read-write mode; the wizard does not close the configurations.
- Verify that the heartbeat connection between clusters is alive by entering hahb -display in the command window.
The state attribute in the output should show "alive". If the state is unknown, then take the ClusterService group offline and bring it online again.