The
A bootable recovery tape can be created from the
It is preferable to use the
IMPORTANT: The media and data format (density and compression) of the installation tape you create must be compatible with the clients on which it will be read. For example, if you have a mixture of DDS4 and DDS5 tape drives on your systems and you wish to be able to read recovery tapes on any of them, you must only use DDS4 media, as DDS5 media will not work in DDS4 drives.
The contents of the system recovery image will always include all files and directories that are considered essential to bringing up a functional system. This essential list is predefined by make_tape_recovery and is located in the following file:
/opt/ignite/recovery/mnr_essentials
In addition to the essential list, data can be included in the recovery image on a disk/volume group, file, or directory basis. Nonessential files and directories can also be excluded.
The tape created by make_tape_recovery is completely
Additional files needed for booting and installing are copied from
/opt/ignite/boot/Rel_release and /opt/ignite/data to the LIF volume on the tape, so everything the system needs to recover is there.
NOTE: During the recovery process, when the file system is set up and the I/O tree is initialized, tape device files may be mapped differently from when the original recovery tape was made. Therefore, it is possible for a recovery tape to be created with one tape device file, for instance /dev/rmt/0m, and recovered from a different device file, such as /dev/rmt/2m, though the physical device is the same.
You can also replicate a system and create a recovery image that can be used for installing clients. The section, “Notes on cloning systems” (page 219) describes how to make use of this process. For additional information regarding system cloning, see the Successful System Cloning using
IMPORTANT: If you use make_tape_recovery for recovery, your tapes must be clearly labeled with the
Recovery tape creation examples
The following examples are intended to assist you in using the make_tape_recovery tool.
System recovery 201