How to migrate HP-UX workloads between physical and virtual servers easily

2
Introduction
With the increasing success of cloud adoption, your IT department is under tremendous pressure to keep pace with
business demand. Your IT directors are concerned about the challenges associated with the rush to cloud-based
services. How can IT maintain adequate security, ensure service levels, and integrate cloud-based services with
existing traditional IT systems? HP offers a solution providing flexibility for automated migrations of HP-UX workloads
between physical and virtual systems, helping IT departments to develop proactive strategies and better sustain
customer demands.
Understand the components and mechanisms involved in system migrations (OS, applications, and data) within
HP Matrix Operating Environment (Matrix OE) infrastructures with a specific focus on HP-UX, HP Integrity Virtual
Machines, and HP Integrity Blade Servers. Virtual to physical (V2P), physical to virtual (P2V), and physical to
physical (P2P) offline migrations are discussed. The required configuration steps for achieving such migrations
are also presented.
For a better understanding of the content of this document, you should be familiar with the HP Insight Management
software stack and its terminology. Insight Management and Matrix OE documentation can be found at
hp.com/go/matrixoe/docs. A basic knowledge of the HP Virtual Connect technology is also required to leverage
the information in this white paper. See hp.com/go/virtualconnect for more information.
Use cases
With virtual to physical moves, you can speed up the migration of projects from the development phase into a test or
qualification phase or a pre-production state. Then use the efficient physical to virtual migration facility to easily and
quickly come back into a development state.
Also use physical to virtual moves for consolidation purposes or during a maintenance campaign where firmware and
low-level drivers have to be upgraded.
Use physical to physical moves during maintenance campaigns and when it is desirable to move workloads from an older
server onto a more recent hardware, such as during a migration from Integrity blades BL860c to BL860c i2. We call this
type of migration physical to physical prime (P2P’) because the physical target server is not identical to the source.
Such moves (V2P, P2V, and P2P’) are also called “cross-technology or unlike” moves, since the source and target are
different by nature.
Note: Virtual to virtual migrations (V2V) do not belong to cross-technology migrations. They are not included in the scope of this document. V2V moves are
explained in the HP Integrity VM installation and administrator guide located at hp.com/go/hpux-hpvm-docs.