HP-UX Virtual Partitions Administrator Guide (includes A.05.07) (5900-1229, September 2010)

/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 293) 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 293) 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 287) 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 283).
Expert recovery works as documented in the Ignite-UX manual; however, you must account
for the vPars differences described in “Expert Recovery” (page 294).
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 at:
http://docs.hp.com/en/vse.html#Virtual%20Partitions
• Ignite-UX and other Curses Applications On the virtual console, when using applications
that use curses, such as the terminal versions of Ignite-UX and SAM, do not press Ctrl-A to
toggle to the console display window of another virtual partition while you are still within
the curses application. This is especially applicable when you are using vparboot -Iand
the Ignite-UX application to install vPars. For more information on curses, see the
curses_intro(3X) manpage.
As with most curses applications, if you get a garbled display, you can press Ctrl-L to refresh
the display.
• ServiceGuard ServiceGuard is supported with vPars. However, because ServiceGuard is
used to guard against hardware failures as well as software failures, its functionality will
be reduced if a cluster includes multiple virtual partitions within the same server. Such
configurations are not recommended. See the ServiceGuard documentation for more
information on running ServiceGuard with vPars.
22 Introduction