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
6
group dgVM and configuring the VxVM disk group vmdatadg on top of it are given later in this
document.
Similarly, in a Metrocluster SRDF environment, this disk group should be configured as an SRDF
device group. In a Metrocluster Continuous Access EVA environment, this disk group should be
configured as an EVA data replication (DR) group.
Tables 1 and 2, respectively, describe the VxVM disk group layouts on Node1 and Node2, and on
Node3 and Node4.
Table 1: VxVM layout on Node1 and Node2
VxVM DG Logical volumes Local/Shared Purpose
Vmpriosdg osvol Local Contains the OS image
Vmpriexedg oraclevol Local Contains the Oracle binaries
Vmdatadg datavol Shared Contains the Oracle database
Table 2: VxVM layout on Node3 and Node4
VxVM DG Logical volumes Local/Shared Purpose
Vmsecosdg osvol Local Contains the OS image
Vmsecexedg oraclevol Local Contains the Oracle binaries
Vmdatadg datavol Shared Contains the Oracle database
Figure 2 shows the storage layout of the VxVM disk groups configured for setting up the virtual
machine.