Strategies for Replicating HP-UX 11i Virtual Systems onto Physical and Virtual Integrity Servers

ManualsBrandsHP ManualsSoftwareHP Matrix Operating Environment w/Insight Control 24x7 Supp Tracking Lic

Strategies for Replicating HP-UX 11i Virtual Systems

onto Integrity Physical and Virtual Machines

Introduction......................................................................................................................................... 2

Integrity Virtual Machine Basics for System Replication............................................................................. 4

Integrity Virtual Machine Mass Storage Overview................................................................................ 4

Virtual Disk Drives ........................................................................................................................ 4

Attached I/O Devices – Tape and Optical Media ............................................................................ 4

Virtual Device Identification and Removal........................................................................................ 5

Planning the Deployment ...................................................................................................................... 5

Local Cloning and Deployment.............................................................................................................. 6

Options for Deployment Depending on Connectivity............................................................................. 6

Remote Cloning and Deployment........................................................................................................... 6

Golden Images ................................................................................................................................ 6

Recovery Media............................................................................................................................... 6

Integrity Virtual Machines’ hpvmclone and hpvmmigrate Tools............................................................. 7

Summary ............................................................................................................................................ 7

For more information............................................................................................................................ 8

Websites......................................................................................................................................... 8

Product Documentation ..................................................................................................................... 8

White Papers................................................................................................................................... 8

Summary of content (8 pages)

PAGE 1
Strategies for Replicating HP-UX 11i Virtual Systems onto Integrity Physical and Virtual Machines Introduction......................................................................................................................................... 2 Integrity Virtual Machine Basics for System Replication............................................................................. 4 Integrity Virtual Machine Mass Storage Overview ..............................................................................
PAGE 2
Introduction The HP Integrity Virtual Machines (Integrity VM) product provides an ideal solution for development, evaluation, and qualification of new software application stacks. Once validation of such configurations is complete, administrators frequently need to replicate them on multiple systems, both virtual as well as physical. This white paper addresses two basic use cases – local and remote – for replication of systems running on Integrity Virtual Machines.
PAGE 3
Figure 1 - Local cloning and replication using us a network installation server, ver, e.g., an Ignite-UX Ignite server. Figure 2 - Local cloning ng and replication using usin DRD cloning so that replicated systems boot from SAN storage.
PAGE 4
Figure 3 - Remote cloning and rep replication using g system images placed on sequential media. Integrity Virtual Machine Basics for System Replication Integrity Virtual Machine Mass Storage Overview HP Integrity Virtual Machines provides a high level of flexibility when configuring storage for virtual machines, including virtual irtual DVD, virtual disks, tape, optical media burners,, and media changer devices.
PAGE 5
You need only execute this command once after installing the device on the physical VM Host system. This creates device special files in /dev/rscsi enabling Integrity VM’s attached I/O functionality. Suppose that the physical VM Host system has a tape drive with device special filename /dev/rmt/c6t1d0 that your virtual machine requires access to.
PAGE 6
Local Cloning and Deployment Options for Deployment Depending on Connectivity There are several approaches available for cloning systems using either storage area network (SAN) or local area network (LAN) connectivity. When the source and target systems are both virtual machines and they share connection to the same SAN, then using the approach described in the white paper Using Dynamic Root Disk to Clone Integrity Virtual Machines is very convenient.
PAGE 7
Integrity Virtual Machines’ hpvmclone and hpvmmigrate Tools Two tools – hpvmclone and hpvmmigrate – are provided with the Integrity VM product that may be used for system replication, but are not solutions by themselves. The hpvmclone command duplicates the configuration of a given virtual machine on the same Integrity VM Host system. The new system will be identical in all aspects, including its virtual CPU attributes, memory size and functionality, and I/O configuration.
PAGE 8
For more information Websites www.hp.com/go/integrityvm www.hp.com/go/ignite-ux Product Documentation Available from docs.hp.com:  Dynamic Root Disk Administrator's Guide  Ignite-UX Administration Guide  HP Integrity Virtual Machines Installation, Configuration, and Administration White Papers Available from docs.hp.