HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

UNIX offering. The DC-OE includes HP-UX vPars and Integrity VM (BB068AA) and the
VirtualBase bundle.
• HP-UX 11i High Availability OE (HA-OE)
For customers requiring continuous access to data and applications, the HA-OE delivers the
protection of Serviceguard and related software. The HA-OE also delivers all the software in
the Base OE plus what has shipped until now in the Enterprise OE.
Table 8 lists the HP-UX 11i v2 to HP-UX 11i v3 supported OE server upgrades.
Table 8 Supported Operating Environments
New 11i v3 Operating EnvironmentsOriginal 11i v2 Operating Environments
Base OEFoundation OE
Base OETechnical Computing OE
Virtual Server OEEnterprise OE
Data Center OEMission Critical OE
NOTE: Many software subsystems require upgrades on the 11i v2 Integrity VM server before
updating to HP–UX 11i v3. The most obvious of these is that Integrity VM must be upgraded to
V3.0 or V3.5 before beginning the HP-UX upgrade. Other layered products, such as Serviceguard,
require version upgrades before updating the operating system to 11i v3. Analyze each layered
product for required upgrades.
Remove HP Integrity Virtual Machines Manager Version 3.0 or earlier before upgrading to Integrity
VM Version 6.1. After installing Integrity VM V6.1, install Integrity Virtual Server Manager V6.1
and HP-UX GUID Manager V1.0. If you are upgrading an Integrity VSP from 11i v2 to 11i v3 and
are using Veritas file systems and volumes, update to Veritas V5.0 and become familiar with the
Veritas 5.0 Installation Guide.
4.1.3 Decide whether to perform a cold-install or an update
The preferred method for upgrading an HP-UX 11i v2 based Integrity VSP to an 11i v3 based VSP
is to use the Update-UX program. The update-ux command takes as input the new 11i v3 OE
depot. The update-ux command strives to maintain all your current user, storage, and network
configurations. There are some 11i v2 multipath solutions that are not compatible with 11i v3. This
same set of multipath solutions must be dealt with whichever method you choose. In most cases,
the multipath conversion is to use the agile devices on 11i v3 in place of the device names that
the multipath solutions invented. The Update-Ux program also strives to keep volume definitions
the same. This is helpful because a cold-install most likely changes all the device names requiring
a mapping of devices to volumes and to guests.
One reason to choose a cold-install over an update-ux update is the ease by which you can
immediately return to the 11i v2 environment. The update-ux path changes the original 11i v2
system configuration making a restore from backups the only way to return to the original 11i v2
system. The cold-install can and should be given separate disks to use allowing the original 11i
v2 system disks to remain unchanged. Because the original disks can remain unchanged, there is
less of a need to back up the 11i v2 based Integrity VSP.
NOTE: HP recommends a full back up of both the Integrity VSP and guests before updating.
Whether an update-ux or a cold-install upgrade is chosen, the administrator needs to study the
documentation that covers the differences between HP-UX 11i v2 and HP-UX 11i v3. To obtain
input on potential upgrade problems, the administrator should also run the HP-UX msv2v3check
tool.
48 Upgrading the VSP from previous versions of Integrity VM