Cluster Server 7.4 Agent for EMC SRDF Configuration Guide - Windows
- Introducing the agent for EMC SRDF
- Configuring the agent for EMC SRDF
- Testing VCS disaster recovery support with EMC SRDF
- How VCS recovers from various disasters in an HA/DR setup with EMC SRDF
- Testing the global service group migration
- Testing disaster recovery after host failure
- Testing disaster recovery after site failure
- Performing failback after a node failure or an application failure
- Performing failback after a site failure
- Setting up fire drill
About configuring system zones in replicated data clusters
In a replicated data cluster, you can prevent unnecessary SRDF failover or failback by creating system zones. VCS attempts to fail over applications within the same system zone before failing them over across system zones.
Configure the hosts that are attached to an array as part of the same system zone to avoid unnecessary failover.
Figure: Example system zone configuration depicts a sample configuration where hosta and hostb are in one system zone, and hostc and hostd are in another system zone.
Use the SystemZones attribute to create these zones.
Modify the SystemZones attribute using the following command:
hagrp -modify grpname SystemZones hosta 0 hostb 0 hostc 1 hostd 1
The variable grpname represents the service group in the cluster.
Global clusters do not require system zones because failover occurs on a remote cluster if all local targets have been exhausted.
When the SRDF runs on R2 devices, SRDF does not synchronize data back to the R1 automatically. You must update out-of-synch tracks manually. Monitor the number of out-of-synch tracks by viewing the ResourceInfo attribute of an online SRDF resource. If the value is too high, update tracks to the R1 using the update action. The update action is defined as a supported action in the SRDF resource type.