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
16
Complete the following steps to create a modular package using Metrocluster Continuous Access
XP/P9000:
1. Run the following command to include the Metrocluster Continuous Access XP/P9000 module in
the existing Serviceguard modular package configuration file:
# cmmakepkg –i /etc/cmcluster/guest-name/guest-name.config –m dts/mcxpca
MC_guest-name.config
Note: When using Metrocluster Continuous Access EVA and Metrocluster SRDF, include dts/mccaeva and
dts/mcsrdf modules respectively.
2. Edit the MC_guest-name.config file to configure the following Metrocluster parameters:
dts_pkg_dir /etc/cmcluster/vmmetro
DEVICE_GROUP dgVM
FENCE never
HORCMINST 0
HORCMPERM MGRNOINST
HORCTIMEOUT 360
MULTIPLE_PVOL_OR_SVOL_FRAMES_FOR_PKG 0
WAITTIME 300
AUTO_FENCEDATA_SPLIT 1
AUTO_NONCURDATA 0
AUTO_PSUEPSUS 0
AUTO_PSUSSSWS 0
AUTO_SVOLPFUS 0
AUTO_SVOLPSUE 0
AUTO_SVOLPSUS 0
Note: If you are using Metrocluster Continuous Access XP version A.09.00, Metrocluster Continuous Access EVA
A.04.00 or Metrocluster SRDF A.07.00, only dts_pkg_dir appears as part of package configuration file. You
must create the Metrocluster environment file, edit the environment file to set parameters, and then distribute the
Metrocluster environment file to all nodes in the cluster. Refer to the next section, “B. Creating a legacy style
Metrocluster package,“ to learn how to create and distribute the Metrocluster environment file.
3. Verify and then apply the package configuration:
# cmcheckconf -v -P /etc/cmcluster/guest-name/MC_guest-name.config
# cmapplyconf -v -P /etc/cmcluster/guest-name/MC_guest-name.config
4. Run the Metrocluster package in the primary data center.
# cmrunpkg vmmetropkg.
After this procedure, the VM configured as a Metrocluster package will run on the primary data
center.
B. Creating a legacy style Metrocluster package
If the Serviceguard package is created using legacy style, then only a legacy style Metrocluster
package can be created. To create a Metrocluster package for a VM guest, you need to distribute the
Metrocluster environment file on all the nodes. Complete the following procedure to configure a
Metrocluster XP environment file on one of the nodes in the primary data center. If you are using
Metrocluster 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 data center, 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