Ignite-UX Frequently Asked Questions

to do so can cause problems with subsequent recoveries.
===============================================================================
4.11
Q: How do I perform two-step recovery?
A: 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:
- In the "Creating Your Own Installation Media" chapter of the
"Ignite-UX Administration Guide", available in the Information
Library.
- In the "Ignite-UX Custom Configuration Files White Paper",
available in the Information Library, locate the following section:
"How do I create the CD equivalent of a tape created by
make_tape_recovery?".
Note: /opt/ignite/data/scripts/examples/make_media_install
is an example script 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.
===============================================================================
4.12
Q: How do I retain custom minor number for device files?
A: 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
look at the setting of '/dev/async' (the minor number) to ensure
it is as it should be for this system.
2. Write a startup script that looks at '/dev/async' and verifies
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.
Note: If the '/dev/async' device file needs to be customized, make
the change before the database starts.
===============================================================================
4.13
Q: How do I recover a system which has Cluster-wide Device Special File (cDSF)
configured?
A: Starting from Version 7.16.x Ignite-UX supports cDSF. No additional steps
are required to recover a system on which cDSF have been configured. The
consistency of cDSF is not checked across the systems sharing the storage
during recovery and the cDSF are not synchronized. The user is responsible
for ensuring the same.
===============================================================================
----------------------------------------
5. General Installation
----------------------------------------
5.1
Q: How does Ignite-UX estimate needed file system sizes? Does it do
anything other than add up the impacts statements?