Installing and Managing HP-UX Virtual Partitions (includes A.04.03)

Crash Processing and Recovery
Network and Tape Recovery
Chapter 10
239
Network and Tape Recovery
This section covers different methods of network and tape recovery on vPars systems. For information on
performing a recovery using:
• make_net_recovery within a vPars-environment, see “Using make_net_recovery within a vPars
Environment” on page 240
• make_tape_recovery outside of a vPars-environment, see “Using make_tape_recovery Outside of a vPars
Environment” on page 242
• make_tape_recovery within a vPars-environment in conjunction with an Ignite-UX boot server, see
“Using make_tape_recovery and Dual-media Boot” on page 246
• make_tape_recovery within a vPars-environment, see “Using make_tape_recovery within a
vPars-environment on PA-RISC Servers (vPars A.03.03, A.04.03)” on page 247
• golden images for recovery, see the whitepaper Using Golden Images with Virtual Partitions
• peripheral boot devices, see the whitepaper Booting, Installing, Recovery, and Sharing in a vPars
Environment from DVD/CDROM/TAPE/Network
• Ignite-UX, including make_net_recovery and make_tape_recovery, see the manual Ignite-UX
Administration Guide and the manpages make_tape_recovery (1m) and make_tape_recovery (1m).
The whitepapers listed above are available at the HP Documentation web site:
http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions
NOTE Using vparboot -I with Ignite-UX on PA-RISC systems
When using Ignite-UX version C.06.xx or later, note that the bootable kernel path has changed
from /opt/ignite/boot/WINSTALL in Ignite-UX B.05.xx and earlier
to /opt/ignite/boot/Rel_B.11.NN/WINSTALL in Ignite-UX C.06.xx and later
Thus, when using Ignite-UX C.06.xx or later, you must specify the absolute path for the
bootable kernel for the vparboot -I command line.
For more information and an example, see “(PA-RISC only) The WINSTALL Boot Kernel Paths
with Different Versions of Ignite-UX and the vparboot -I command” on page 22.
NOTE Supported Tape Devices
Note that you can use only the tape devices that are already supported for PA-RISC servers in
standalone mode; vPars does not support devices beyond what is supported by the server itself.