HP-UX HB v13.00 Ch-17 - vPars
HP-UX Handbook – Rev 13.00 Page 21 (of 46)
Chapter 17 Virtual Partitions (vPars)
October 29, 2013
Updating the vPars Product
There are three different possible reason to update:
Updating from a vPars version to a newer one of the same release, e.g. from
A.04.xx to A.04.yy
Updating from vPars A.03.xx to A.04.xx with update-ux (PA-RISC only)
Update from vPars A.04.xx to A.05.xx with update-ux (Integrity only)
All the steps are described in the manual “Installing and Managing HP-UX Virtual Partitions
(vPars)”, e.g. http://www.docs.hp.com/en/T1335-90057/T1335-90057.pdf.
It is possible to use update-ux to upgrade HP-UX 11i v1 with vPars A.03.xx to HP-UX 11i v2
with vPars A.04.xx in one go. Please follow the upgrade steps described in chapter 4 of the
manual “Installing and Managing HP-UX Virtual Partitions”
(http://docs.hp.com/en/6769/T1335-90038.pdf). It is recommended to save the first virtual
partition as the last one to upgrade and to upgrade the other virtual partitions first. This ensures
all other vPars have finished their upgrade, when the nPar reboots after the upgrade.
Ignite-UX Recovery
For information on Ignite-UX refer to http://docs.hp.com/en/IUX
Making an Archive of a Virtual Partition
For vPars version A.03.02 and earlier, and A.04.01 make_tape_recovery cannot be used to
recover a system from within a virtual partition, although it has been supported on vPars enabled
servers from A.02.03. However recovery using tapes must then be done outside vPars. You need
to use make_net_recovery. The program make_net_recovery works the same for making
archives of both non-vPars and vPars hard partitions.
With the A.03.03 release of vPars, make_tape_recovery is now supported as a recovery method
within a virtual partition. A recovery tape being created by the make_tape_recovery command
on a tape device connected to the vPar can be used for recovery the same way as a “normal”
system.
A new device attribute similar to a boot device is being added to the virtual partition resource
definitions. It is called TAPE. Here is an example:
# vparcreate -p vpar2 -a io:1/0/14/0/0/4/0.5.0:TAPE
vparstatus –v shows: