Implementing disaster recovery for HP Integrity Virtual Machines with Metrocluster and Continentalclusters on HP-UX 11i
Table Of Contents
- Executive summary
- Introduction
- Audience
- Configuring Integrity Virtual Machines as packages in HP Metrocluster
- Verifying failover of Metrocluster packages across data centers
- Troubleshooting Metrocluster VM problems
- Application startup and monitoring
- Configuring Integrity Virtual Machines as packages in HP Continentalclusters
- Overview
- Software requirements for HP VMs in Continentalclusters
- Configuring HP VM packages in Continentalclusters
- Creating VM switches in all nodes of the primary cluster
- Configuring replicated storage for VM in Continentalclusters
- Installing the operating system on the virtual machine
- Testing the virtual guest OS in all nodes of the primary cluster
- Creating VM switches in all nodes of the recovery cluster
- Preparing the replicated storage for use in the recovery cluster
- Creating the virtual machine in all nodes of the recovery cluster
- Testing the virtual guest OS in all nodes of the recovery cluster
- Resynchronizing the replicated storage
- Packaging the HP VM in the primary cluster and the recovery cluster
- Creating a Continentalclusters package
- Creating a Continentalclusters configuration with the VM packages
- Running the Continentalclusters monitoring daemon in the recovery cluster
- Recovering to the recovery cluster
- Related documentation
- Appendix I
- Appendix II
- For more information
- Call to action
27
nodes. Complete the following procedure to configure a Metrocluster XP environment file on one of
the nodes in the primary cluster. If you are using Metrocluster Continuous Access EVA or Metrocluster
SRDF, refer to Appendix II for the detailed steps.
For Metrocluster Continuous Access XP:
1. On one of the node in primary cluster, copy the data replication environment file “xpca.env” from
the directory
/etc/cmcluster/toolkit/SGCA to the package directory as <package>_xpca.env.
2. Edit the data replication environment file.
AUTO_SVOLPSUE=0
AUTO_SVOLPFUS=0
AUTOPSUEPSUS=0
AUTO_FENCEDATA_SPLIT=1
AUTO_SVOLPSUS=0
AUTO_NONCURDATA=0
MULTIPLE_PVOL_OR_SVOL_FRAMES_FOR_PKG=0
WAITTIME=300
PKGDIR=/etc/cmcluster/ccvm
FENCE=never (or data or async as the case may be)
DEVICE_GROUP=dgVM
CLUSTER_TYPE=”continental”
HORCTIMEOUT=360
3.
Once the <package>_xpca.env file has been modified for the specific package, copy this file to
all nodes in both primary and recovery clusters.
Creating a Continentalclusters configuration with the VM packages
Once the HP VMs are packaged as Continentalclusters packages, the packaged VMs must be
configured as recovery groups in the Continentalclusters configuration.
Edit the recovery group information to have the VM packages in both the primary and recovery
clusters and re-apply the configuration.
Running the Continentalclusters monitoring daemon in the recovery cluster
Once the Continentalclusters configuration is successfully applied, start the monitoring package
ccmonpkg in the cluster recovery_cluster.
Recovering to the recovery cluster
When the primary cluster fails, the HP VM packages can be recovered in the recovery cluster. The
recovery can be done by issuing the
cmrecovercl command. The cmrecovercl command can be
issued only when there is at least one alert for the primary cluster.
# cmrecovercl –f