As of Ignite version C.7.7, make_[tapenet]_recovery has a -uoption that will update the client Ignite software to the version on the server specified by the -soption. For more information, see make_net_recovery(1M) or make_tape_recovery(1M).

Recovery image creation process

The process of creating a recovery image using Ignite-UX is described as follows:

1.Prepare the client.

The make_net_recovery command and the make_tape_recovery -s command first check that the recovery tools installed on the client are compatible with the version on the Ignite-UX server as described in “Reconciling client and server Ignite-UX versions for recovery” (page 194).

2.Create files and directories for the recovery image.

The make_net_recovery and make_tape_recovery -s commands create a new directory for the client on the server in /var/opt/ignite/clients if needed. For make_tape_recovery run on the client without the -s option, the config files and log files are created in the /var/opt/ignite/recovery directory on the client.

The commands generate a timestamp for naming the recovery archive, the configuration, and the configuration directory. The directory containing the configuration files for the recovery image is similar to the following:

/var/opt/ignite/clients/client/recovery/2005-03-17,11:19

The corresponding recovery archive is named 2005-03-17,11:19 , and is in the

/var/opt/ignite/recovery/archives/client directory.

The timestamp is important for coordinating configuration files and recovery archives, and for ongoing recovery image management.

An overview of the files is as follows:

/var/opt/ignite/clients/client

CINDEX client_name client_status config.sys host.info hw.info install.log recovery/

client_status defaults

latest -> 2005-03-17,11:19

2005-03-17,11:19/ archive_content system_cfg archive_cfg control_cfg recovery.log flist manifest

The archive_content file contains keyword and volume/disk/directory pairs that are used to generate the flist file, which defines the contents of the recovery image. See make_net_recovery(1M) and make_tape_recovery(1M) for more information on inclusion and exclusion of files in the recovery image.

System recovery 195