The make_net_recovery tool creates a system recovery image and stores it on a system that may be accessed using the network. The recovery image created by make_net_recovery is specific to the system it was created for and its identity includes hostname, IP address, networking information, etc. In the event of a root disk failure, the recovery image can be installed using Ignite-UX to recover the system.
The contents of the system recovery image will always include predefined files and directories that are considered essential to bringing up a functional system. By running make_net_recovery in interactive mode (with the -ioption), the directories and files that make up the essential list can be displayed. 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 included. See “Recovery Image Contents” (page 190) for more information.
Network Recovery Server Dependency
The recovery images created by make_net_recovery are designed to work with an Ignite-UX server; you cannot remove your Ignite-UX server and still use your recovery image.
Networking Features
Two NFS mount points are established on the client by make_net_recovery. The /var/opt/ ignite/clients directory on the Ignite-UX server is mounted to the client system to store configuration files that describe the client configuration and location of the recovery image. The second mount point is made to the archive_server:archive_dir (see the -aoption) and is used to store the recovery image of the client system. The default storage location on the Ignite-UX server is /var/opt/ignite/recovery/archives. After successful or unsuccessful creation of the system recovery image, the NFS mount points are unmounted.
The NFS mount for the recovery image directory may be exported on a per-client basis. A separate recovery image directory is used for each client. This enables you to NFS export each directory only to the individual client owning the recovery image, which provides security.
NOTE: If clients obtain temporary IP addresses from DHCP that differ from the IP address that they use during normal operation, you must allow the client access to all of the possible IP addresses to ensure access to the recovery image. If you do not, the client may fail to mount the recovery image directory from the NFS server and the recovery will fail.
Log Files
On an Ignite-UX server, progress and errors are logged to:
/var/opt/ignite/clients/client/recovery/datetime/recovery.log
On a local system, progress and errors are logged to:
/var/opt/ignite/recovery/datetime/recovery.log
Adding Clients for Recovery
You can add a new client to your Ignite-UX server for the purpose of creating recovery images if the client is already running HP-UX. Unlike installation, adding a client for recovery does not require you to reboot the client. This is useful when you have installed the operating system, customized it, and now want to be able to recover it in the event of a problem or for disaster recovery purposes.
To add a new client to your Ignite-UX server, and then create a system recovery image, use the following steps:
