Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

3DC_TOPOLOGY multi-target-bi-link
For Multi-Hop Bi-Link configuration, specify "multi-hop-bi-link":
3DC_TOPOLOGY multi-hop-bi-link
c. Specify the DC1 nodes for the DC1_NODE_LIST parameter:
DC1_NODE_LIST “dc1_node1 dc1_node2”
d. Specify the DC2 nodes for the DC2_NODE_LIST parameter:
DC2_NODE_LIST “dc2_node1 dc2_node2”
e. Specify the DC3 nodes for the DC3_NODE_LIST parameter:
DC3_NODE_LIST “dc3_node1 dc3_node2”
f. Specify the device group configured between DC1 and DC2 for the
DC1_DC2_DEVICE_GROUP parameter:
DC1_DC2_DEVICE_GROUP dg12
g. Specify the device group configured between DC2 and DC3 for the
DC2_DC3_DEVICE_GROUP parameter:
DC2_DC3_DEVICE_GROUP dg23
This is a phantom device group when using Multi-Target Bi-Link configuration
h. Specify the device group configured between DC1 and DC3 for the
DC1_DC3_DEVICE_GROUP parameter:
DC1_DC3_DEVICE_GROUP dg13
This is a phantom device group when using Multi-Hop Bi-Link configuration
i. Specify the MU# used by the device group configured between DC1 and
DC2(DC1_DC2_DEVICE_GROUP) for the DC1_DC2_DEVICE_GROUP_MU parameter:
DC1_DC2_DEVICE_GROUP_MU <DG12_MU#>
j. Specify the MU# used by the device group configured between DC2 and DC3
(DC2_DC3_DEVICE_GROUP) for the DC2_DC3_DEVICE_GROUP_MU parameter:
DC2_DC3_DEVICE_GROUP_MU <DG23_MU#>
k. Specify the MU# used by the device group configured between DC1 and DC3
(DC1_DC3_DEVICE_GROUP) for the DC1_DC3_DEVICE_GROUP_MU parameter:
DC1_DC3_DEVICE_GROUP_MU <DG13_MU#>
l. Specify one of the following values for the FENCE parameter:
async if the Continuous Access journal pair is configured between DC1
and DC2.
never or data if the Continuous Access synchronous pair is configured between
DC1 and DC2.
FENCE <async or never or data>
m. Specify the RAID Manager instance number for the HORCMINST parameter:
HORCMINST 0
Besides these attributes, there are additional 3DC parameters available in the package
configuration file. It is recommended that the default values of the parameters that are
not listed here are retained unless there is a specific business requirement to change them.
For more information on the additional parameters available in the package configuration
file, see “Environment File Variables for Serviceguard Integration with Continuous Access
P9000 or XP” (page 475).
3. Validate the package configuration file:
# cmcheckconf -P pkgName.config
4. Apply the package configuration file:
# cmapplyconf -P pkgName.config
After the modular recovery package is created in the recovery cluster, if the value of any 3DC
parameter needs to be changed, then edit this package configuration file and re-apply it.
446 Designing a Three Data Center Disaster Recovery Solution