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

Infrastructure requirements for cross-technology moves

Fluid cross-technology offline moves, in a Matrix OE environment, are possible when the following requirements

are met:

• Potential HP Integrity VM hosts and physical Integrity blade targets are registered in the VMM.

• NPIV technology is supported by HP Integrity VM hosts’ targets.

• HP Integrity VM hosts’ hardware database is populated with SAN fabrics and registered in Matrix OE.

• Existence of portability group(s) with both servers with Virtual Connect and HP Integrity VM hosts.

• One or more Storage Pool Entries (SPE) associated to unlike portability groups.

• SAN fabric connectivity (zoning) between SPEs and SAN controllers.

To illustrate the verification of the above requirements, we take a concrete example where we want to perform a

V2P move of a logical server called v2p2v_ls from an HP Integrity VM host (visor1) toward a physical blade server

named Bay4.

Verifying that potential source and target are registered in Matrix OE

Cross-technology offline moves can only happen between servers (Integrity blades or HP Integrity VM hosts) fully

registered in the Matrix OE. We perform this operation by running the Configure Managed System Setup

Wizard tool (MSSW). Consult the HP Matrix OE getting started guide for more details about the MSSW at

hp.com/go/matrixoe/docs.

Figure 10. Systems registered in VMM

A sanity check can be obtained by looking for the VMM status, green icon from the VM column of the All Systems

view. Figure 10 shows our physical target (USE7224K6D) and HP Integrity VM host (visor1) fully registered in VMM.

Another level of verification can be performed at the Servers tab of HP infrastructure orchestration.

The Compute Resources view must explicitly list the potential servers used for cross-technology moves (figure 11).