The make_tape_recovery tool creates a bootable tape that can be used to restore a system using the system’s tape drive. Remember that make_tape_recovery is subject to the requirements and limitations inherent with tape media:

•A tape drive must be available on each system to be archived.

•If you want to save previous recovery images, remove the tapes containing the existing recovery images from the tape drives before creating new ones.

•If a recovery image exceeds the capacity of a tape, you need to swap tapes for both creation and extraction.

•If you want to make sure that the newly created tapes are good, you must check the log files on the system.

•Tape drives are more error prone than a local network.

Recovery image configuration policies

When specifying recovery image content for make_[tapenet]_recovery, the following rules apply:

•No essential file or directory can be excluded.

•Files and directories inside an included directory will be included recursively.

•If an essential file or directory exists outside the root disk or volume group, the disk or volume group it resides in is included in the recovery image. If you want to include all the files within that disk or volume group in the recovery image, use the make_[tapenet]_recovery -Aor -xoptions.

•If a symbolic link to a file or directory is included, only the link will be included in the recovery image. The actual file or directory is not included unless it is specified or the symbolic link is essential. A warning will be given when an item is only a symbolic link.

•If a directory is included that contains symbolic links to other files or directories, the symbolic links will be included but not the referenced files or directories, unless they too are included. No warnings are given regarding these links.

•If a directory contains local mount points, the files and directories under the local mount points are not included, by default. This policy can be waived by specifying the option inc_cross (include directories and cross-mount points) in the selection interface or command line.

•In case of conflicting entries in the selections, exclusions take precedence over inclusions.

•File system volume size must provide 10 percent free space for each volume - Ignite-UX automatically modifies the file system volume size accordingly. For more information, see the description of the _hp_addnl_fs_free_pct variable in instl_adm(4).

Reconciling client and server Ignite-UX versions for recovery

If you initiate a recovery from the server GUI and the client system has a lower version of Ignite-UX than the server does, Ignite uses swinstall to update the existing Ignite-UX software on the client. If the client system does not have Ignite installed, a small subset of Ignite-UX software will be installed. (The small subset of Ignite-UX software is not a full Ignite-UX server installation, and does not provide Ignite-UX server capability to the client.)

If you initiate a recovery from the client with make_tape_recovery -sor make_net_recovery -s, and the client system has a lower version of Ignite-UX than the server does, behavior depends on the degree of version mismatch. If the version letters don't match, such as C.x.x and B.x.x, Ignite will display an error and the process will stop. If the version numbers do not match, Ignite will display a warning and the process will continue.

In any case, if the server has a lower version of Ignite-UX than the client, a message to this effect will be displayed and the process will stop.

194 Recovery