HP Serviceguard Metrocluster manual Deleting the Continentalclusters configuration

Deleting the Continentalclusters configuration

The cmdeleteconcl command is used to delete the configuration on all the nodes in the Continentalclusters configuration. To delete Continentalclusters and the Continentalclusters configuration run the following command.

# cmdeleteconcl

While deleting a Continentalclusters configuration with the recovery group maintenance feature, the shared disk is not removed. Before applying a fresh Continentalclusters configuration using an old shared disk, you must re-initialize the file system in the shared disk using the mkfs command.

Checking the Version Number of the Continentalclusters Executables

For Continentalclusters version A.08.00, use what command to get the versions of the executables.

For example,

# what /usr/sbin/cmviewconcl

Maintaining the data replication environment

Continentalclusters supports the pre-integrated physical replication solutions using Continuous Access P9000 and XP, Continuous Access EVA, EMC Symmetrix Remote Data Facility, and 3PAR Remote Copy.

•See, “Maintaining Continuous Access P9000 and XP Data Replication Environment” (page 63) for administering Continentalclusters when the Continentalclusters solution is built on Continuous Access P9000 and XP for the physical data replication.

•See, “Maintaining Metrocluster with Continuous Access EVA P6000 data replication environment” (page 65) for administering Continentalclusters when the Continentalclusters solution uses Continuous Access EVA.

•See, “Maintaining EMC SRDF data replication environment” (page 66) for administering Continentalclusters when the Continentalclusters uses EMC SRDF data replication solution.

•See, “Maintaining 3PAR Remote Copy data replication environment” (page 66) for administering Continentalclusters when the Continentalclusters uses 3PAR Remote Copy data replication solution.

Maintaining Continuous Access P9000 and XP Data Replication Environment

Resynchronizing the device group

After certain failures, data is no longer remotely protected. In order to restore disaster-tolerant data protection after repairing or recovering from the failure, you must manually run the command pairresync. This command must run successfully for disaster-tolerant data protection to be restored. Following is a partial list of failures that require running the pairresync command to restore disaster-tolerant data protection:

•Failure of ALL Continuous Access links without restart of the application.

•Failure of ALL Continuous Access links with Fence Level DATA with restart of the application on a primary host.

•Failure of the entire recovery Data Center for a given application package.

•Failure of the recovery P9000 and XP disk array for a given application package while the application is running on a primary host.

Deleting the Continentalclusters configuration 63