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

Following are the topics discussed in this section:
“Configuring Complex Workload Packages to Use CFS” (page 133)
“Configuring Complex Workload Packages to Use SG SMS CVM or Veritas CVM in Legacy
Style Package” (page 133)
“Configuring Complex Workload Packages to use SLVM” (page 133)
“Halting the Complex Workload in the Primary Cluster” (page 133)
Configuring Complex Workload Packages to Use CFS
When the storage for the complex workload is configured on a Cluster File System (CFS), the
complex workload package must be configured to depend on the MNP package managing CFS
mount point through package dependency. With package dependency, the Serviceguard package
that starts the complex workload will not run until its dependent MNP package managing CFS
mount point is up, and will halt before the MNP package managing CFS mount point is halted.
Set up the following dependency conditions in the Serviceguard package configuration file:
DEPENDENCY_NAME <cfs_mp_pkg_name_dep>
DEPENDENCY_CONDITION <cfs_with_mp_pkg_name>=UP
DEPENDENCY_LOCATION SAME_NODE
Configuring Complex Workload Packages to Use SG SMS CVM or Veritas CVM in Legacy Style
Package
NOTE: HP recommends you to use the modular style of packaging.
When the storage for the complex workload is configured on CVM disk groups, the complex
workload package must be configured to depend on the CVM disk group multi-node package
through package dependency. With package dependency, the Serviceguard package that starts
the complex workload will not run until its dependent CVM disk group multi-node package is up,
and will halt before the CVM disk group multi-node package is halted.
Set up the following dependency conditions in the Serviceguard package configuration file:
DEPENDENCY_NAME <cvm_dg_pkg_name_dep>
DEPENDENCY_CONDITION <cvm_dg_pkg_name>=UP
DEPENDENCY_LOCATION SAME_NODE
Configuring Complex Workload Packages to use SLVM
When the complex workload required storage is configured on SLVM volume groups, the complex
workload package must be configured to activate and deactivate the required storage in the
package control script for Legacy style packages and in the package configuration file for Modular
style packages.
As an example, let us consider a Legacy complex workload package. Modify the package control
script to activate the volume group in shared mode and set VG in the package control script for
SLVM volume groups.
VG[0]=<vg_name>
VGCHANGE="vgchange -a s
Halting the Complex Workload in the Primary Cluster
You need to first halt the complex workload stack on the node in the primary cluster using the
cmhaltpkg command.
Support for Complex Workloads in a Continentalclusters Environment using SADTA 133