HP-UX Virtual Partitions Administrator's Guide (includes A.05.02)

Crash Processing and Recovery
Network and Tape Recovery
Chapter 10
327
Using make_tape_recovery within a vPars-environment on PA-RISC Servers
(vPars A.03.03, A.04.03, A.05.01)
For PA-RISC servers, beginning with vPars A.03.03 for HP-UX 11i v1 and A.04.03 for HP-UX 11iv2, vPars
supports tape drives. This includes recovery of a virtual partition within a vPars environment and without
using an Ignite-UX server as a boot helper.
Requirements and the BOOT Attribute
To use the tape device during a recovery, you must meet the following requirements:
the tape device must be owned by the target virtual partition (the partition that is being recovered)
the tape drive must be connected through an external SCSI device or be internal to the machine
the tape device must be an explicitly specified resource with the attribute TAPE. This is similar to
specifying the boot device with the attribute BOOT. For example:
# vparcreate -p winona2 -a io:1/0/14/0/0/4/0.5.0:TAPE
or
# vparmodify -p winona2 -a io:1/0/14/0/0/4/0.5.0:TAPE
Please note that when modifying io resources, the target virtual partition must be in the down state.
The vparstatus -v command should show the tape device with the TAPE attribute:
# vparstatus -p winona2 -v
[Virtual Partition Details]
Name: winona2
.
.
.
[IO Details]
1.0.14
1.0.12
1.0.14.0.0.4.0.10.0.0.0.0.0 BOOT
1.0.14.0.0.4.0.5.0.0.0.0.0 TAPE
.
.
.
Archiving
The process of creating an archive is the same as for non-vPars OS instances:
# make_tape_recovery -A -a /dev/rmt/1mn
Recovering
To begin recovery, boot the target virtual partition using the tape drive as specified with the TAPE attribute:
winona1# vparboot -p winona2 -B TAPE
Then proceed with the recovery as normal.
NOTE The system may appear but is actually not hung when booting from tape due to the increased
time it takes to load a kernel from tape instead of from disk.