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

15
Creating a portability group with Virtual Connect Servers and
HP Integrity VM hosts
The potential physical servers and HP Integrity VM hosts’ targets for V2P and P2V migrations must be part of the same
portability group. From the HP Matrix OE Visualization, select Modify  Logical Server
Portability Groups, and click on Create Group.
Fill the Group Name and Group Description fields and then, in the Targets Table, tick the
Server with Virtual Connect domain group as well as desired HP Integrity VM hosts. Click on the
Add Selection button; review the configuration of this new Portability Group; Save it; and exit with Done.
Figure 13 shows a portability group called Integrity V2P2V containing physical blades from the ATC_VCDG
VC domain group and HP Integrity VM host visor1.
Figure 13. Creating an unlike portability group
Creating SPE in unlike portability groups
Logical servers take their storage information from the SPE defined in the Matrix OE database. During logical server
activation, the LSM will use information contained in SPEs and ask the underlying layers to setup the SAN connections.
By definition, SPEs are tied to portability groups and for achieving V2P or P2V migrations, we need to create at least one
SPE in our unlike Integrity V2P2V Portability Group.
Note: To keep this document simple, easy to read, and for didactic purpose the example below may not strictly follow storage best practices.
From the HP Matrix OE visualization, open the Modify  Logical Server Storage Pools. In the portability
group pull down menu, select Integrity V2P2V. Click on the Add Entry button (bottom right)
Supply a Storage Entry Name if the default one does not fit your need. Also supply a Storage Entry
Description and select HP-UX in the Storage Entry Operating System pull down menu. Click on the
Add Port button and select ATC_RACK(FC) in the Fabric column. Click again on the Add Port button and
select ATC_RACK0(FC) in the Fabric column.