HP-UX 11i v3 Installation and Update Guide, March 2013

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, see the make_tape_recovery( 1M) manpage
on an Ignite-UX server or the Ignite-UX Administration Guide (http://www.hp.com/go/
ignite-ux-docs).
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 on the active system does not go as planned, you can boot the
pre-updated clone by entering:
drd activate x reboot=true
If you do boot the pre-update clone, and subsequently decide to re-activate the updated image,
you can use the same drd activate command noted above, as the use of this command will
always set the primary boot path to the inactive image.
If the SoftReboot feature has been installed on your system, then it can be used with the following
command:
drd activate -x softreboot=true
SoftReboot is supported with the HP-UX 11i v3 September 2011 (and later) OEUR and should be
installed before cloning. For information on supported systems, see SoftReboot White Paper at
http://www.hp.com/go/hpux-core-docs-11iv3.
NOTE: If you have updated from 11i v2 to 11i v3 on the active system image, you can go back
and forth between the inactive 11i v2 image and the updated 11i v3 image by ensuring the
following:
When an HP-UX 11i v2 system is booted and HP-UX 11i v3 is installed on the inactive image,
you should not use any sw* commands with drd runcmd. Use of this operation would invoke
11i v3 libraries and executables, which can make system calls not supported on the 11i v2
kernel.
When an HP-UX 11i v3 system is booted and HP-UX 11i v2 is installed on the inactive image,
you can run drd runcmd swlist or drd runcmd swverify; however, you cannot run
any other sw* commands.
The drd clone contains the entire contents of the root volume group, and thus has all the components
that are essential to bringing up a functional system.
In addition to system recovery, DRD has other uses, all of which can reduce downtime. These
include system maintenance, patching, testing, and provisioning. See “Reducing downtime using
Dynamic Root Disk (page 29) for more information, including links to documentation and a website.
Part II: Backing up your data files
Depending on your system backup needs and your configuration, there are a number of different
backup methods from which to choose. Two possible backup methods are as follows:
HP Data Protector
HP-UX fbackup/frecover utilities
24 Before you begin