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

make_net_recovery(1M) make_net_recovery(1M)
Warning: Setting _hp_ignite_sw_impact to 1 may cause recoveries to fail if any file system sizes
are reduced below the minimum required.
Note that changes to the system_cfg file must be done after a preview has been created (-p). After making
the above changes, resume the creation of the tape recovery archive (-r).
File Names with Non-Printable Characters
Although permissible within HP-UX, it is inadvisable to use characters that do not have a printable graphic
on the hardware you commonly use, or that are likely to confuse your terminal. Filenames with these char-
acters cause a warning message to be displayed by make_net_recovery. In addition, files that con-
tain these non-printable characters are not included in the archive.
Running Commands in Single User Mode
HP recommends that the make_tape_recovery and make_net_recovery commands be run in
default mode of multi-user (run level 3 or 4 depending on how the system is configured). However, HP
does support execution of make_tape_recovery in single-user mode using the supported method doc-
umented in Ignite-UX FAQs. (See Section 11, Network/Tape Recovery, Question 23.) A copy of the
Ignite-UX FAQs is installed with Ignite-UX in /opt/ignite/share/doc/FAQ, and the latest version
of the Ignite-UX FAQ may be obtained by sending an email to [e-mail]
does not recommend running make_net_recovery in single-user mode.
Non-Responding NFS Servers
The make_tape_recovery and make_net_recovery tools can handle non-responding auto-
mounted file systems accessed via indirect maps or the -hosts map without hanging. However, the tools
will hang if there are automounted file systems accessed via direct maps or directly mounted NFS file sys-
tems.
Unmounted File Systems in /etc/fstab file
If unmounted file system in /etc/fstab is detected, a WARNING message will be displayed and the
make_tape_recovery and make_net_recovery will complete with return code 2.
Data Recovery from Raw Logical Volumes
Only file system data is included in recovery archives created by make_net_recovery. Data included
in raw logical volumes (like those that contain database data) is not included in recovery archives, and must
be backed up as part of the overall backup stategy of a system.
Auto Port Aggregate (APA) Cloning Limitation
If a system has an auto port aggregate (APA) configured, Ignite-UX does not support cloning using that
recovery archive. It is only supported to recover the archive to the system on which it was created. This
assumes that the lan interfaces are still configured for APA, on the switch they are connected to, in exactly
the same way as when the archive was created.
LVM Volume Groups Having Volume Group Version 2.0 or 2.1 Are Not Supported
Ignite-UX does not support the system recovery archive creation using the make_net_recovery com-
mand for Volume Groups having Volume Group Version 2.0 or 2.1. If any LVM Volume Group having
unsupported Volume Group Versions is provided as arguments to make_net_recovery command, the
command fails and reports the unsupported volume groups. In such situations, either omit the unsupported
volume groups as input to make_net_recovery command or migrate all those unsupported volume
group version to 2.2 or higher (using LVM’s Volume Group Version migration tool, vgversion) and rerun
the command.
DEPENDENCIES
The Ignite-UX GUI must be run from the Ignite-UX Server, see ignite(5). make_net_recovery
depends on several other Ignite-UX tools. When running the Ignite-UX server GUI, Ignite-UX checks
whether the client system that make_net_recovery runs on has the same versions of Ignite-UX tools.
If running make_net_recovery from the command line without ever interacting with the Ignite-UX
GUI, commands will need to be installed using swinstall(1M) from the Ignite-UX server to the client sys-
tem on which make_net_recovery will be run.
make_net_recovery requires the following filesets of the Ignite-UX product be installed on the
9