Ignite-UX Reference (March 2010, B3921-90005)

make_net_recovery(1M) make_net_recovery(1M)
Using the Recovery Archive
To recover a failed system using the network recovery archive:
• If the client system is being replaced, or the LAN card has changed since
make_net_recovery was last used, you should manually rename the old client directory
prior to starting the recovery. Not doing so will cause a new directory to be created and you
will not see the recovery archives created under the old client directory. To rename the client
directory, obtain the new LAN address (you can use the LanAddress boot-ROM com-
mand in the information menu), then use the mv command. For example:
cd /var/opt/ignite/clients
mv 0x00108305463A 0x0060B0C43AB7
If you have already booted the new system, you will need to remove the new client before
renaming the old directory. Be careful not to remove the old directory containing the recovery
information.
• Boot the system using either a network boot, a tape created using make_boot_tape,or
using the bootsys command if the system is still running.
• Do not interact with ISL.
• Select: [ Install HP-UX ].
• From the Ignite-UX GUI, select the icon for the client.
• Choose Install/New Install.
• Select the recovery configuration to use.
Exporting Archive Directory
The directory used to store the archives must be exported from the archive server to each client. Exporting
the archive directory from the system where the archive will be stored enables make_net_recovery to cre-
ate and access the archive via NFS. The archive server by default is the Ignite-UX server but may be
changed using the -a option to be a different remote server, or even the local client if you want to capture
the archives as part of the client’s regular backup. Note however, that if the archives are stored on the client
itself, they must be put onto a remote server if the client ever needs to be recovered using them.
For security reasons, it is best to export each client-specific archive directory to just the individual client. If
the recovery archive creation is initiated from the ignite GUI on the Ignite-UX server, and the archive
server is the same as the Ignite-UX server, the /etc/dfs/dfstab or /etc/exports file will be
edited automatically so the archive may be stored in the desired location. Otherwise, if
make_net_recovery is run directly on the client, the following steps are required to be performed on
the archive server.
• On the archive server, create a directory for each client to contain the archive of the client’s files. It is
important that the directory be owned by the user bin. Replace client in the commands below with
the hostname of the client. If you use the -a option to make_net_recovery to specify an alter-
nate location for the archives, you will need to use that path instead of the default which is shown
below.
mkdir -p /var/opt/ignite/recovery/archives/client
chown bin:bin /var/opt/ignite/recovery/archives/client
• For 11.31 or later, edit /etc/dfs/dfstab to add an entry for each client. Replace client with the
client’s fully qualified hostname in the example shown:
share -F nfs -o sec=sys,anon=2,rw=client
/var/opt/ignite/recovery/archives/client
For other releases, edit /etc/exports to add an entry for each client. Replace client with the
client’s hostname in the example shown:
/var/opt/ignite/recovery/archives/client -anon=2,access=client
• For 11.31 or later, run the shareall command to have the edits to the exports file take effect:
/usr/sbin/shareall -F nfs
For other releases, run the exportfs command to have the edits to the exports file take effect:
5