make_net_recovery.1m (2012 03)

m
make_net_recovery(1M) make_net_recovery(1M)
• 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. Export-
ing the archive directory from the system where the archive will be stored enables make_net_recovery
to create 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 cap-
ture 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
alternate 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:
/usr/sbin/exportfs -av
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 which describe the client configuration and location of the recovery archive. The
second mount point is made to the archive_server:archive_directory (see the
-a option) and is used to
store the recovery archive of the client system. After successful or unsuccessful completion of the system
recovery archive, the NFS mount points are unmounted.
The NFS mount for the archive directory may be exported on a per-client basis. A separate archive direc-
tory is used for each client. This allows the NFS export of each directory only to the individual client
owning the archive, which provides security.
If the default NFS mount options are unsuitable for your network environment, you can pre-mount those
directories with whatever options are necessary.
make_net_recovery will discover that they are
already mounted and not attempt to mount them. For example, you can do the following if the read and
write buffers had to be 1KB in size:
mount -F nfs -orsize=1024,wsize=1024 archive_server:archive_directory \
/var/opt/ignite/recovery/arch_mnt
mount -F nfs -orsize=1024,wsize=1024 archive_server:/var/opt/ignite/clients \
/var/opt/ignite/recovery/client_mnt
The actual arguments must match those for the -a option if it is used in the first mount command.
If the client system does not have the most recent versions of Ignite-UX tools, the Ignite-UX GUI uses
swinstall to install the recovery package which includes all necessary files to perform the
recovery.
HP-UX 11i Version 3: March 2012 − 5 − Hewlett-Packard Company 5