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

Archiving and Recovering a Virtual Partition Using Another Virtual Partition as the Ignite-UX Server
Archiving the Virtual Partitions Using a Virtual Partition as the Ignite-UX Server
The following steps describe how one or more virtual partitions can be archived using
make_tape_recovery. These first steps describe how to create a disaster recovery tape.
1. One of the virtual partitions is an Ignite server. Its root disk is the one that is booted first,
when the vPars Monitor is booted. It has the vPars Monitor (/stand/vpmon) and the vPars
database (/stand/vpdb) that is used to bring up virtual partitions in the nPartition. It must
also have a tape drive which will be used by make_tape_recovery in step (3). This tape
drive will also be used in step (4) to boot the tape created in step (3) thus it must be available
to the nPartition at boot time.
2. The Ignite server makes recovery tapes of all the other virtual partitions using
make_net_recovery. This is done when the Ignite server is running in a virtual partition,
archiving the other virtual partitions while they are running.
3. The Ignite server makes a recovery tape of the system it is running on using
make_tape_recovery and “normal” filesystem recovery tapes. This is performed while
the Ignite server is running in a virtual partition. It allows the Ignite server to archive itself
while the other virtual partitions are running production work. The tape created by
make_tape_recovery in this step will have:
• The data necessary to recover the Ignite server on a “cold” system (nothing running on
it, including vPars).
• The files required by vPars: the vPars Monitor (/stand/vpmon) and the vPars database
(/stand/vpdb).
• The files created in step (2) by make_net_recovery. These files will be used to recover
the other virtual partitions in step (8).
• Normal filesystem recovery archive of the Ignite server.
Recovering the Virtual Partitions Using one of the Virtual Partitions as the Ignite-UX Server
4. The nPartition must have a tape drive available to boot from. Note that nothing is running
in the nPartition. Boot the make_tape_recovery tape created in step (3) in an nPartition.
The system is being booted without vPars at this point.
5. Recover the Ignite server that was archived to tape in step (3). This is done using the
make_tape_recovery tape that was booted in step (4) along with normal filesystem
recovery.
6. Reboot the nPartition, this time using the root disk that was recovered in step (5). Stop at
the MON> prompt.
7. Use vparload at the MON> prompt to load the virtual partition recovered in step (5). This is
the Ignite server.
8. Use vparboot -I to recover the other virtual partitions using the make_net_recovery
files created in step (2).
9. There may be normal filesystem recoveries that need to be done to fully recover the virtual
partitions after they are booted in step (8).
10. Modify the autoboot string (using mkboot -a ...) so that the virtual partitions will
autoboot at the next system boot.
11. Reboot the nPartition to test if all the virtual partitions come up as expected.
290 Crash Processing and Recovery