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
12
13. Deport the disk group.
# vxdg deport vmdatadg
14. Restore the device groups to its original state.
For Metrocluster Continuous Access XP/P9000, re-establish the CA link by issuing the following
command on any node in the cluster:
# pairresync –g dgVM
For Metrocluster SRDF, re-establish the SRDF link by issuing the following command on any node in
the cluster:
# symrdf –g dgVM establish
For Metrocluster Continuous Access EVA, use HP StorageWorks Command View EVA to fail-back
the DR group to its original site.
Now that the storage system is configured for the virtual machine, the next step is to create the virtual
machine.
Creating a virtual machine
After configuring the VM network and VM storage, the virtual machines need to be created on all the
cluster nodes. On each cluster node where you installed Integrity VM, create the virtual machine. All
the nodes in the primary site use vmpriosdg, vmpriexedg, and vmdatadg as guest storage for virtual
machine vmmetro. All the nodes in the recovery site use vmsecosdg, vmsecexedg, and vmdatadg as
guest storage for vmmetro.
1. On each node in the primary site, import the disk groups vmpriosdg, vmpriexedg, and vmdatadg
and create the virtual machine vmmetro.
# hpvmcreate –P vmmetro –a dvd:scsi::disk:/var/os/hpvm.0505_OE.Gold1.iso\
–a disk:scsi::lv: /dev/vx/rdsk/vmpriosdg/osvol \
–a disk:scsi::lv: /dev/vx/rdsk/vmpriexedg/oraclevol \
–a disk:scsi::lv: /dev/vx/rdsk/vmdatadg/datavol \
–a network:lan:[hardware-address]:vswitch:vs1 \
–I vmmetro –O hpux
The VM host ISO file /var/os/hpvm.0505_OE.Gold1.iso is used to install the OS into the guest
device.
The guest virtual network device information consists of the following fields, separated by colons:
• Network
• Adapter-type—can be either
lan or avio_lan
• [hardware-address] (optional)—formatted as
bus,device,mac-addr
If you do not specify the hardware address—or specify a portion of it—the information is
generated for you. HP recommends allowing Integrity VM to generate the hardware address.
The hardware address consists of the following information:
–
bus—virtual network device PCI bus number
–
device—virtual network device PCI slot number
–
mac-addr—the virtual network device MAC address in either of the following formats:
0xaabbcc001122 or aa-bb-cc-00-11-22.
– The MAC address that you enter is checked to make sure it does not conflict with any of the
VM host’s physical network adapter MAC addresses.
• vswitch—virtual switch information, formatted as
vswitch:vswitch-name (where vswitch-
name
is the name assigned to the virtual network switch when you create it using the hpvmnet
command)
Note: For online migration of a VM guest in a Metrocluster environment, it is required that the VM guest created
in all the nodes of the Metrocluster have the same “mac-addr” for each virtual network device.