Filter
Top Products
Preparing to Migrate to HP-UX 11i v2
Backing Up Your System
Chapter 4 73
The contents of the system recovery archive always includes all files and
directories which are essential to bringing up a functional system. This
“essential” list is pre-defined by make_net_recovery. You can run
make_net_recovery in its interactive mode to review the directories and
files which make up the “essential list,” and also add or remove other
data from the archive on a disk/volume group, file, or directory basis.
For more information on using make_net_recovery, see the
make_net_recovery (1M) manpage or the Ignite-UX Administration
Guide.
Using make_tape_
recovery
The Ignite-UX server’s make_tape_recovery command creates a
bootable recovery tape for an LVM or whole disk file system while it is up
and running. When a system has a logical volume layout, the recovery
tape will only include data from the root volume group, plus data from
any non-root volume group containing the /usr directory.
You can run make_tape_recovery either on the Ignite-UX server or
locally on the system from which you are trying to make a recovery tape.
To create the bootable recovery tape, enter:
/opt/ignite/bin/make_tape_recovery -Av
where: v is for verbose mode and A specifies the entire root disk or
volume group. Also, more than one volume group can be specified with
the -x option.
If a tape drive other than the default (/dev/rmt/0m) will be used, modify
the command to point to the device you want to use, for example a tape
drive at /dev/rmt/3mn:
/opt/ignite/bin/make_tape_recovery -Av -d /dev/rmt/3mn
To recover a failed system disk or volume group after a recovery tape has
been made, simply load the recovery tape, boot the system, interrupting
the boot sequence to redirect to the tape drive. Allow the install process
to complete. Do not intervene. The system will reboot and, because map
files for all associated volume groups have been saved on the tape, any
other existing volume groups are imported and mounted automatically.
Data which is not in the root volume group must be backed up and
recovered using normal backup utilities.