HP-UX 11i v3 Installation and Update Guide, September 2009 (Update 5 Release)

The contents of the OS recovery image always includes all files and directories that are
essential to bringing up a functional system. This essential list is predefined by
make_net_recovery.
For more information on using make_net_recovery, refer to the
make_net_recovery(1M) manpage or the Ignite-UX Administration Guide (http://
docs.hp.com/en/oshpux11iv3.html#Ignite-UX).
Choosing make_tape_recovery
The Ignite-UX product’s make_tape_recovery command creates a bootable OS
recovery tape for a system while it is up and running. When a system has a logical
volume layout, the recovery tape (by default) only includes data from the root volume
group, plus data from any non-root volume group containing the /usr directory.
You can run make_tape_recovery locally on the system from which you are trying
to make an OS recovery tape. Data that is not in the root volume group must be backed
up and recovered using normal backup utilities.
For more information on using make_tape_recovery, refer to the make_tape_recovery(
1M) manpage on an Ignite-UX server or the Ignite-UX Administration Guide (http://
docs.hp.com/en/oshpux11iv3.html#Ignite-UX).
Choosing drd clone
The drd clone command allows you to create an OS recovery image, referred to as
an inactive clone, on a free internal or SAN disk. For recovery purposes, all you need
to run is
drd clone –t target_dsf
where target_dsf is the device special file of the spare disk.
In the event that the update to HP-UX 11i v3 on the active system does not go as
planned, you can activate and boot the HP-UX 11i v2 clone in minutes by entering:
drd activate –x reboot=true
If you do activate and boot the HP-UX 11i v2 clone, then decide to re-activate the HP-UX
11i v3 image on the original disk, you can use the same drd activate command
noted above, as the use of this command will toggle between the original disk and the
clone disk.
Backing up your system 29