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

3. dts/dts/dts_pkg_dir
This variable specifies the absolute path to the Site Controller Package directory. This directory
must be present in all the nodes in the Metrocluster. The Site Controller Package looks for the
Metrocluster environment file in this directory. All Metrocluster flag files must be created within
this directory.
4. monitor_interval
This attribute specifies the time interval, in seconds, at which the Site Controller Package
monitors the complex-workload packages. The default value is 30 seconds. Values lesser than
30 seconds cause the Site Controller Package to check the monitor package status more
frequently.
To migrate the Site Controller package, use the -u option with the cmmakepkg command.
1. Run the following command to upgrade the Site Controller Package:
cmmakepkg -u pkg_name -m dts/sc output_pkg.ascii
2. Copy the values of the attributes to the new package ASCII file.
For example:
For Metrocluster with Continuous Access for P9000 and XP, run the following command:
cmmakepkg -i output_pkg.ascii -m dts/mcxpca -t path to the environment file
migrated_output_pkg.ascii
For Metrocluster with Continuous Access EVA
cmmakepkg -i output_pkg.ascii -m dts/mccaeva -t path to the environment file
migrated_output_pkg.ascii
For Metrocluster with EMC SRDF
cmmakepkg -i output_pkg.ascii -m dts/mcsrdf -t path to the environment file
migrated_output_pkg.ascii
3. Use the cmcheckconf command to validate the package.
cmcheckconf -P migrated_output_pkg.ascii
4. Use the cmapplyconf command to add the package to the Serviceguard configuration.
cmapplyconf -P migrated_output_pkg.ascii
Monitoring Complex Workload Packages
The monitoring, and initiation of a site failover are dependent on how the complex-workload
packages are configured in the Site Controller Package. When the Site Controller Package is
started on a site, it starts all the packages of a complex workload at that site. The Site Controller
Package then monitors the packages that are configured as a critical_package on the site.
When no critical_package is configured, the Site Controller Package monitors all the packages
that are configured as managed_package.
The Site Controller Package initiates a site failover under the following circumstances:
• All the nodes in the current site have failed or the site is lost in a disaster.
• The monitored packages have failed in the cluster (that is, not administratively halted).
When multiple packages are configured using the critical_package attribute, the Site Controller
Package will initiate a failover even if one of these critical packages have failed. When there are
no packages configured with the critical_package attribute, the Site Controller Package will
initiate a failover only when all the monitored packages have failed in the cluster.
When a monitored package is an MNP package, the package is considered failed only if the last
instance to go down has failed and is not administratively halted. In case of failover packages,
the package is considered failed only when a package is down due to its service or resource
342 Designing a Disaster Recovery Solution Using Site Aware Disaster Tolerant Architecture