Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

Live Application Detach
There may be circumstances in which you want to do maintenance that involves halting a node,
or the entire cluster, without halting or failing over the affected packages. Such maintenance might
consist of anything short of rebooting the node or nodes, but a likely case is networking changes
that will disrupt the heartbeat. New command options in Serviceguard A.11.20 (collectively known
as Live Application Detach (LAD)) allows you to do this kind of maintenance while keeping the
packages running. The packages are no longer monitored by Serviceguard, but the applications
continue to run. Packages in this state are called detached packages. When you have done the
necessary maintenance, you can restart the node or cluster, and normal monitoring will resume
on the packages. For more information on the LAD feature, see Managing Serviceguard A.11.20
available at http://www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard.
NOTE: Live Application Detach feature is not supported in SADTA environment.
HP vPars and HP Integrity VM
Configuring virtual machine using HP Integrity Virtual Machines (VM) or HP-UX Virtual Partitions
(vPars 6) as a package in Metrocluster or Continentalclusters provides remote data protection of
applications running inside the virtual machine. In addition, it simplifies the geographical movement
of the virtual machine from one site to another in case of site outages and it ensures high availability
of the virtual machine within the site.
This configuration protects the VM environment from disasters that result in the failure of an entire
data center. For more information on the configuration, see the white paper Implementing disaster
recovery in virtualized environment using HP vPars and HP Integrity VM with Metrocluster and
Continentalclusters on HP-UX 11i available at http://www.hp.com/go/hpux-serviceguard-docs
—> HP Serviceguard Metrocluster with EMC SRDF.
Checking the Metrocluster package configuration
Starting HP Serviceguard version A.11.20, the cmcheckconf -v command validates the cluster
and the package configuration. Starting April 2011 patch release, Metrolcuster uses this functionality
to ensure the sanity of Metrocluster and the Site Controller package configuration. HP recommends
that you set up a cron job to regularly run the cmcheckconf command. For more information
about setting the cron job, see Setting up Periodic Cluster Verification section in the latest version
of the Managing Serviceguard manual available at http://www.hp.com/go/hpux-serviceguard-docs
—> HP Serviceguard.
“Validating Metrocluster package” (page 52) lists the checks made on a Metrocluster Package.
Table 4 Validating Metrocluster package
RemarkCommandValidations/Checks
For Metrocluster with EMC SRDF, it
checks whether the SYM CLI is installed.
cmcheckconf [–v]
cmapplyconf
Check whether the Array Management
Software is available.
cmcheckconf [-P/-p]
cmcheckconf [-v]Check whether the contents in the
environment file matches with the
contents in the package present in the
CDB.
Checks the package configuration file
that is passed as an argument for the
cmcheckconf [–v]
cmapplyconf
Check all attributes in the Metrocluster
module.
cmcheckconf [-P/-p] command.
cmcheckconf [-P/-p]
For cmcheckconf, it checks the
Metrocluster environment file that is
52 Metrocluster features