User's Guide

are used as your choice of data replication method, configure and apply them as described in the
next sections before applying the Continentalclusters configuration.
Table 10 shows the types of packages that are needed for each type of data replication.
Table 10 Continentalclusters Data Replication Package Structure
Recovery ClusterPrimary Cluster
Data Replication
Receiver Package
Recovery Application
Package
Data Replication
Sender Package
Primary Application
Package
Replication Type
NoYesNoYesP9000 or XP Series
Continuous Access
NoYesNoYesEVA Series Continuous
Access
NoYesNoYesSymmetrix/EMC SRDF
NoYesNoYes3PAR Remote Copy
YesYesNoYesOracle Standby Database
Configuring a Cluster without Recovery Packages
Use the following steps and the instructions described in chapters 4 through 7 of Managing
Serviceguard user’s guide as guidelines for creating a new cluster or preparing an existing cluster
to run in a Continentalclusters environment:
1. If creating a new cluster, install required versions of HP-UX and Serviceguard. Also, if using
an existing cluster, upgrade to the versions of HP-UX and Serviceguard that are required for
Continentalclusters. See the Continentalclusters Release Notes for specifics on your versions
requirements. Coordinate with the recovery site to make sure the same versions and patches
are installed at both sites.
2. Set up all cabling, being sure to provide redundant disk storage links and network connections.
3. Configure the disks and filesystems. Set up data replication (logical or physical).
4. Configure the cluster according to the instructions in chapter 5 of the Managing Serviceguard
user’s guide. Use the cmapplyconf command to apply the cluster configuration. Then test
the cluster.
5. Starting with Continentalclusters A.08.00, packages in Continentalclusters can be configured
as modular packages. For information about configuring primary and recovery packages as
modular, see “Configuring Primary and Recovery Packages as Modular Packages” (page 67).
Configure and test each primary package according to the instructions in chapters 6 and 7
of the Managing Serviceguard user’s guide. Use the cmapplyconf command to apply the
package configuration.
6. Be sure that AUTO_RUN is set to NO in the package ASCII configuration file for any package
that is in a recovery group, and therefore might at some time be a candidate for recovery.
This is to ensure that the package will not be automatically started if the primary site tries to
come up again following a primary site disaster.
If changing the setting of the AUTO_RUN parameter to NO in the ASCII configuration file for
an existing package, then re-apply the configuration using the cmapplyconf command.
NOTE: When package switching is disabled, a package does not automatically start at
cluster startup time. Therefore, setting AUTO_RUN(PKG_SWITCHING_ENABLED) to NO means
that primary packages in recovery groups must be started manually on the primary cluster.
They also must be manually enabled for local switching, using the cmmodpkg -e
<packagename> command.
Preparing the Clusters 55