Building Disaster Tolerant Serviceguard Solutions Using Metrocluster with Continuous Access EVA
Completing and Running a Continental Cluster Solution with Continuous Access EVA
Chapter 4270
Completing and Running a Continental
Cluster Solution with Continuous Access EVA
The following section describes how to configure a continental cluster
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 Primary Cluster
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 primary
cluster (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 primary cluster:
# mkdir /etc/cmcluster/<package_name>
Create a Serviceguard package configuration file in the primary
cluster.
# 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.