HP-UX Virtual Partitions Administrator Guide (includes A.05.08) (5900-1312, March 2011)

adding up the numbers results in a total of nine CPUs for the server when there are actually
only five physical CPUs.
• (PA-RISC only) The WINSTALL Boot Kernel Paths with Different Versions of Ignite-UX and the
vparboot -I command
The examples in this document use the Ignite-UX bootable kernel WINSTALL path as:
◦ /opt/ignite/boot/WINSTALL
This is the correct path for Ignite-UX versions B.05.xx and earlier. However, if you are using
Ignite-UX version C.06.xx or later, the WINSTALL path has changed to:
◦ /opt/ignite/boot/Rel_B.11.NN/?INSTALL
◦ – where NN completes the HP-UX version and where ? is W for PA-RISC systems
◦ For example, if vPars is using HP-UX 11i v2 (11.23) instances on a PA-RISC server with
Ignite-UX version C.06.xx, the path is:
– /opt/ignite/boot/Rel_B.11.23/WINSTALL
Thus, if you are using HP-UX 11i v2 (11.23) on a PA-RISC server and
◦ Ignite-UX version B.05.xx or earlier:
you should specify /opt/ignite/boot/WINSTALL on the command line
(/opt/ignite/boot is the default); for example
# vparboot -p <target_partition> -I <ignite_server>,/opt/ignite/boot/WINSTALL
◦ Ignite-UX version C.06.xx or later:
you must specify the absolute path /opt/ignite/boot/Rel_B.11.23/WINSTALL
on the command line (because /opt/ignite/boot is the default); for example
# vparboot -p <target_partition> -I <ignite_server>,/opt/ignite/boot/Rel_B.11.23/WINSTALL
• Ignite-UX Recovery and Expert Recovery
Beginning with vPars A.02.03, the creation of make_tape_recovery tapes is supported
on vPars-enabled servers. However, there are limitations:
◦ (PA-RISC Only) Recovery using tapes within the vPars environment is supported beginning
vPars A.03.03, A.04.03, and A.05.01. See “Using make_tape_recovery within a
vPars Environment” (page 265) for more information.
◦ (Integrity Only) Recovery using tapes within the vPars environment is supported on HP
Integrity servers beginning vPars A.04.04, and A.05.02. See “Using
make_tape_recovery within a vPars Environment” (page 265) for more information.
◦ If you are using an earlier release of vPars, you must perform recoveries using
make_tape_recovery tapes outside of the vPars environment. For example, the tape
cannot be used with the vparboot -I command. See “Using make_tape_recovery
Outside of a vPars Environment” (page 261) for a sample disaster recovery recipe that
uses make_tape_recovery.
Ignite-UX Recovery via make_net_recovery requires additional steps as noted in “Network
and Tape Recovery” (page 259).
Expert recovery works as documented in the Ignite-UX manual; however, you must account
for the vPars differences described in “Expert Recovery” (page 266).
For more information on using tape devices, see also the Booting, Installing, Recovery, and
Sharing in a vPars Environment from DVD/CDROM/TAPE/Network white paper available
on the BSC website at:
http://www.hp.com/go/hpux-vpars-docs
HP Product Interaction 21