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

make_tape_recovery(1M) make_tape_recovery(1M)
volumes will no longer be mirrored. They may be manually remirrored after the system is up. Using the
config.local file in the clients directory, you may specify the LVM commands to restore mirrored
disks to be executed automatically after the system has been restored. For more details, see the
/opt/ignite/share/doc/diskmirror.pdf white paper.
File System Volume Size May Be Modified
The file system volume size(s) in the recovery archive may be modified when the archive is installed. By
default, Ignite-UX will ensure 10% free space for each volume and modify the file system volume size
accordingly.
If you do not want Ignite-UX to modify the file system volume size(s) automatically, add:
init _hp_ignore_sw_impact=1
to the /var/opt/ignite/recovery/latest/system_cfg file.
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 network 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_tape_recovery. In addition, files that
contain 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_tape_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_tape_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_tape_recovery command, the
command fails and reports the unsupported volume groups. In such situations, either omit the unsupported
11