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

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.
The term local deployment pertains to scenarios in which the source (virtual) system is connected to the same
storage area network (SAN) or local area network (LAN) as the target system. Figure 1 and Figure 2 illustrate
two of the basic approaches for local system replication. The local replication discussion here will focus
primarily on target systems that are physical Integrity servers. Refer to the HP white paper Using Dynamic Root
Disk to Clone Integrity Virtual Machines available from http://docs.hp.com, for details pertaining to local
replication when the target system is a HPVM virtual machine.
Remote replication refers to the use case where the target system does not share storage or network connectivity
with the source system. The remote replication scenario discussed here is illustrated in Figure 3.
The source system is assumed to be running HP-UX 11iv3, although the same concepts can be applied to an
11iv2 system. The concepts discussed here apply to Integrity Virtual Machines version 3.5, 4.0 and later.