Configuring Primary and Recovery Packages as Modular Packages

In a Continentalclusters configuration, starting with version A.08.00, packages specified as a primary_package or a recovery_package in a recovery group can be configured as a modular package. The packages can be created using any modules supplied with and approved in HP Serviceguard. For example, for the Oracle application, the ECM Toolkit supplied modular package for Oracle can be used to create the primary and recovery packages in the Continentalclusters.

Continentalclusters supports the following pre-integrated physical replication solutions: Continuous Access P9000 or XP, Continuous Access EVA, EMC Symmetrix Remote Data Facility, and 3PAR Remote Copy. When any of these pre-integrated solutions are used, the corresponding Continentalclusters specific module must be included to the primary and recovery packages. For example, while using Continuous Access P9000 or XP replication, the dts/ccxpca module must be used to create the primary and recovery packages.

NOTE: If none of the above pre-integrated physical replications is used, then it is not required to include any Continentalclusters specific module.

The following topics are covered in this section:

•Configuring primary and recovery packages as modular packages when using Continuous Access P9000 or XP

•Configuring primary and recovery packages as modular packages when using Continuous Access EVA

•Configuring primary and recovery packages as modular packages when using EMC SRDF

•Configuring primary and recovery packages as modular packages using 3PAR Remote Copy

Configuring primary and recovery packages as modular packages when using Continuous Access P9000 or XP

When using Continuous Access P9000 or XP replication in Continentalclusters, the primary and recovery packages must be created using the dts/ccxpca module. To use this module, Metrocluster with Continuous Access for P9000 and XP must be installed on all nodes in the Continentalclusters. If Metrocluster with Continuous Access for P9000 and XP is not installed on all the nodes, then the following error message is displayed:

The file <complete_path_to_module_file> does not exist or read/search permission not set for a component of the path:

No such file or directory /etc/cmcluster/modules/dts/mc.2:4: Could not

find include .......

All parameters that were previously available in the Metrocluster environment file are now configured from the package configuration file. When the package configuration is applied in the cluster using the cmapplyconf command, the Metrocluster environment file is automatically generated in the package directory on all nodes in the cluster.

CAUTION: Do not delete the Metrocluster environment file that is generated in the package directory. This file is crucial for the startup of the package in a Continentalclusters.

Complete the following steps to configure primary and recovery packages as modular packages using Continuous Access P9000 or XP with Continentalclusters A.08.00:

Building the Continentalclusters Configuration

67