Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00

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.
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.
NOTE: The Device Group Monitor is not supported for the recovery package.
Configure Continentalclusters and Continentalclusters Recovery Group
Ensure that the Continentalclusters software is installed on all nodes in both primary and recovery
cluster. For each application in the 3DC solution, configure a recovery group using their
corresponding packages at the primary and recovery cluster.
Complete the following steps to configure a recovery group in Continentalclusters:
1. Edit the Continentalclusters configuration file to specify the recovery groups. Specify
the primary package configured in the primary cluster as PRIMARY_PACKAGE and the recovery
package configured in the recovery cluster as RECOVERY_PACKAGE in the recovery group.
For Example:
RECOVERY_GROUP_NAME <recovery_group_name>
PRIMARY_PACKAGE <primary_cluster_name>/<primary_package_name>
RECOVERY_PACKAGE <recovery_cluster_name>/<recovery_package_name>
When deploying complex workloads, specify the Site Controller package configured in the
primary cluster as PRIMARY_PACKAGE and the Site Controller package configured in the
recovery cluster as RECOVERY_PACKAGE in the recovery group.
For Example:
RECOVERY_GROUP_NAME <recovery_group_name>
PRIMARY_PACKAGE <primary_cluster_name>/<site_controller_package_name>
RECOVERY_PACKAGE <recovery_cluster_name>/<site_controller_package_name>
2. Check the configuration file syntax:
# cmcheckconcl -v -C <Continental_cluster_config_file_name>
3. Apply the configuration:
Configuring an application 125