Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

This would backup the entire vg00 volume group and the one file anyFile from the directory
myDataVolume. Assuming that myDataVolume is on the other volume group, the layout of the
other volume group will be saved and restored during recovery (along with anyFile).
During the installation of a recovery archive, the process stopped with a message
from pax_iux complaining of a file with % at the start of its name:
pax_iux:/sbin/%sh text busy, would you like to push a shell
for debugging? What should I do if I encounter this message?
Enter yes to push a shell for debugging, then rename the file that will not conflict with any other
file name. For example:
# mv "/sbin/%sh" "/sbin/%sh.remove"
Then continue the recovery installation process by entering exit 2 and click Return. If you move
the files to a name that has something in common, they will be easier to find and remove post
recovery.
NOTE: Files starting with % (such as/sbin/%sh) are created by Ignite-UX during a recovery or
installation session. These files remain on a system if an error occurred during the last recovery or
installation before they could be cleaned up. Problems during recovery or installation must be
investigated immediately; failing to do so can cause problems with subsequent recoveries.
How do I perform two-step recovery?
When recovering an Itanium-based system from a recovery image created with
make_tape_recovery that does not support Itanium-based tape boot, you must perform a
two-step recovery. This requires both a recovery tape of the system and a bootable CD or DVD
containing the same revision of Ignite-UX, for example, C.6.6.x.
If you are using a version of Ignite-UX that does not have a corresponding set of Operating
Environment media, you must create a custom bootable CD or DVD to recover from the recovery
tape. Instructions on how to create this bootable media are available from the following locations:
• See the chapter Creating Your Own Installation Media in Ignite-UX Administration Guide,
available in the Information Library.
• See the section How do I create the CD equivalent of a tape created by make_tape_recovery?
in Ignite-UX Custom Configuration Files White Paper, available in the Information Library.
NOTE: /opt/ignite/data/scripts/examples/make_media_installis an example
script is delivered with Ignite-UX C.6.2.x and greater. You can use this script as a guideline to
create a bootable CD or DVD that may be used for dual-media recovery.
How do I retain custom minor number for device files?
Ignite-UX provides no functionality to allow you to retain custom settings for minor numbers in
device files. A significant fraction of device files are recreated using the insf -e command after
a recovery or golden image installation. This includes the /dev/async device file (which will be
used in the examples below).
You do have several options:
1. Change your per-system post recovery instructions to remind you to check the setting of /dev/
async (the minor number) to ensure settings are retained prior to recovery process.
2. Write a startup script that looks at /dev/async and verify that it has the minor number you
would expect. If it is not the expected value, recreate it in the startup script. It is important to
note that anyone can run the insf -e command that would create this device file, not just
Ignite-UX during a recovery.
24 Recovery (make_tape_recovery and make_net_recovery)