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

Normal Maintenance
There might be situations when the package has to be taken down for maintenance purposes
without having the package move to another node. The following procedure is recommended for
normal maintenance of the Metrocluster Continuous Access EVA:
1. Stop the package with the appropriate Serviceguard command.
# cmhaltpkg pkgname
2. Distribute the Metrocluster Continuous Access EVA configuration changes.
# cmapplyconf -P pkgname.config
3. Start the package with the appropriate Serviceguard command.
# cmmodpkg -e pkgname
Planned maintenance is treated the same as a failure by the cluster. If you take a node down for
maintenance, package failover and quorum calculation is based on the remaining nodes. Make
sure that the nodes are taken down evenly at each site, and that enough nodes remain on-line to
form a quorum if a failure occurs. See “Example Failover Scenarios with Two Arbitrators” (page 30).
Failback
After resynchronization is complete, halt the package on the failover site, and restart it on the
primary site. Metrocluster will then do a failover of the storage, which will trigger Continuous
Access EVA to swap the personalities between the source and the destination Vdisks, returning
source status to the primary site.
Completing and Running Continentalclusters Solution with Continuous
Access EVA
The following section describes how to configure Continentalclusters solution using Continuous
Access EVA, which requires the HP Metrocluster with Continuous Access EVA product.
NOTE: Make sure to have completed the preparation for the Metrocluster Continuous Access
EVA as described in section, “Preparing a Serviceguard Cluster for Metrocluster Continuous Access
EVA ” on both primary and recovery sites.
Setting up a Primary Package on the
Use the procedures in this section to configure a primary package on the primary cluster. Consult
the Serviceguard documentation for more detailed instructions on setting up Serviceguard with
packages, and for instructions on how to start, halt, and move packages and their services between
nodes in a cluster.
1. Install Continentalclusters on all the cluster nodes in the source disk site (skip this step if the
software has been pre installed).
Run swinstall(1m) to install HP Continentalclusters from an SD depot.
2. When swinstall(1m) has completed, create a directory for the new package in the source disk
site:
# mkdir /etc/cmcluster/<package_name>
Create a Serviceguard package configuration file in the source disk site.
# cd /etc/cmcluster/<package_name>
# cmmakepkg -p <package_name>.ascii
Customize the Serviceguard package configuration file as appropriate to your application.
Be sure to include the pathname of the control script /etc/cmcluster/<package_name>/
<package_name>.cntl for the RUN_SCRIPT and HALT_SCRIPT parameters.
246 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA