15 Recovery
Overview
System recovery restores a recovery image previously created for a specific system, and is useful in the case of hardware or software failure. See the System Recovery section below for more information.
System Recovery
This section assumes you are creating a recovery image to be stored on the
System recovery requires some work before a problem occurs. On a regular basis, you need to run the appropriate tool on each of your systems: make_net_recovery or make_tape_recovery. Use the make_net_recovery command to create a recovery image on another system, or the make_tape_recovery to create a recovery image on tape.
The make_tape_recovery and make_net_recovery commands each create a bootable, installation recovery image that is customized for your machine. Recovery images contain your system’s configuration information (disk layout, etc.) and files from one or more disks. You can exert some control over which files are saved as part of the image - see “Recovery Image Contents” (page 190) for more information.
The make_net_recovery command and the make_tape_recovery command are collectively referred to as: make_[tapenet]_recovery.
You can use the make_[tapenet]_recovery commands on a command line, the
Once you have a recovery image on tape or
1.If a disk failed, replace it.
2.Boot from your recovery tape or system.
3.Wait for the recovery to complete.
4.Once the system comes back up, verify the system configuration and recover the latest copies of files from the last system backup. Ensure that you do not recover operating system files as this can create unexpected results.
If you have SAS devices connected to the recovery client, be aware that as of Ignite version C.7.5, Ignite will recover to the original disk based on WWID, even if it has been moved. However, moving SAS devices can result in a changed device file name. For more information, see the
IMPORTANT: The offline diagnostic environment (ODE) command copyutil is a diagnostic tool for
IMPORTANT: During
188 Recovery