This section only describes the required changes to the package
control script to support the cascading failover configuration.
To create a primary package on the primary cluster, the reader
should follow the procedure in “Setting up a Primary Package on the
Primary Cluster”.
Cascading failover uses a ContinentalClusters in which the
primary cluster is configured as a metropolitan cluster. Therefore,
there are a few differences from the normal ContinentalClusters
configuration in customizing the package control script <package_name>.cntl.
The CLUSTER_TYPE variable should be set to "metro"
The PKGR1SYMGRP variable should be set to the Symmetrix device group
name that was defined in the primary Symmetrix.
The PKGR2SYMGRP variable should be set to the Symmetrix device group
name that was defined in the secondary Symmetrix
The elements of the R1HOST array variable should be set to the hostnames
of the systems that connect to the primary Symmetrix
The elements of the R2HOST array variable should be set to the hostnames
of the systems that connect to the secondary Symmetrix
Before
executing the cmapplyconf on the primary cluster, make sure to split
the SRDF logical links, between the primary Symmetrix and the secondary
Symmetrix, for the disks associated with the application package.
Run the following command on a node that connects to the primary
Symmetrix:
# symrdf -g <prisymdevgrpname> split -v
Printable version
