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
Configuring the RVG service group IP resource for failover
Modify the IP resources in the RVG service group to ensure the desired failover behavior in the RDC.
In the event of a system or Exchange failure, VCS attempts to fail over the Exchange service group to another system within the same RDC system zone. However, in the event that VCS fails to find a failover target node within the primary zone, VCS switches the service group to a node in the current secondary system zone.
Use the following procedure to modify the IP resources.
Note:
For IPv6 networks, modify the IPv6 resources.
To modify the IP resources in the RVG service group
- From VCS Cluster Explorer, in the left pane, select the RVG service group (EXCH_RVG_SG).
- In the right pane, select the Resources tab.
- Right-click the RVG IP resource and select View > Properties View.
- In the Edit Attributes window, edit the Address attribute.
Select Per System.
Select the first node in the primary zone and enter the virtual IP address for the primary zone.
Select the second node in the primary zone and enter the virtual IP address for the primary zone (the same IP address as the first node).
Repeat for all nodes in the primary zone.
Select the first node in the secondary zone (SYSTEM3) and enter the virtual IP address for the secondary zone.
Select the second node in the secondary zone and enter the virtual IP address for the secondary zone (the same IP address as the first node in the secondary zone).
Repeat for all nodes in the secondary zone.
Click OK.
- In the Properties View window, verify that all nodes in the primary zone have the same IP address. Also verify that all nodes in the secondary zone have the same IP address. The IP address at the primary zone and the secondary zone should be different
- This step is applicable only if you are using a non-shared storage environment (VMNSDg agent).
In the Edit Attributes window, edit the MACAddress attribute as follows:
Select Per System.
From the dropdown list, select the node in the RDC primary zone.
In the Scalar Value field, enter the physical address (MAC address) of the network interface card (NIC) to be monitored on the primary zone system.
Use the ipconfig -all command to retrieve the physical address.
From the dropdown list, select the node in the RDC secondary zone.
In the Scalar Value field, enter the physical address (MAC address) of the network interface card (NIC) to be monitored on the secondary zone system.
Use the ipconfig -all command to retrieve the physical address.
Click OK.
- In the Properties View window, verify that the MACAddress attribute for the nodes in the primary and secondary zone are different.
- Close the Properties View window.
Since this is the final task in configuring the RVG service group for the primary and secondary zones, you can now bring the RVG service group online in both the primary and secondary zones.