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

20
Figure 20. Configuring HP AVIO Stor EFI drive to enumerate all FC LUNs
Verify that the HP-UX OE, which is going to be installed on this system, contains the HPPortableImage bundle,
then proceed to the installation using your preferred method.
Note: The HPPortableImage bundle is selected by default starting with HP-UX 11i v3, March 2012. For previous HP-UX versions, manually select it or
download it from software.hp.com.
Once the OE is deployed and the network is fully configured and operational, then you can login as a privileged user and
modify the gio_portable_image kernel parameter as follow:
# kctune gio_portable_image=1
This command will trigger a snapshot of the network configuration in the persistent KRS database during next clean
shutdown as shown in Figure 4.
V2P offline move
The first step to perform, in order to achieve a V2P cross-technology move, is to gently shutdown the logical server
(shutdown -hy now). This is needed to gently close the running applications and to save the network configuration
in the persistent KRS database.
Then, select the logical server from the Logical Server perspective in the HP Matrix OE visualization
and click on Tools Logical ServersMove. The list of all possible targets is displayed. Select a physical target
(Figure 21), click on Move and then Confirm.
Figure 21. Physical V2P targets
The following screen (Figure 22) lists the different steps achieved by LSM, VMM, VCEM/VCM, and the vmVirtProvider
during the V2P offline move operation. The first step is an abrupt power-off of the server in case it has not been done
previously. The virtual machine is then unregistered (placed in a Non-Runnable state) in the source host. The logical
server definition and meta-information (i.e., EFI boot entry) are passed to the VCM, which creates a suitable profile and
assigns it to the target physical server. The physical server is powered on and boots automatically from the SAN.
During boot time, the HPPortableImage bundle forces the system to use the saved network instances.