modifies the file system volume size accordingly. If you do not want Ignite-UX to modify the file system volume sizes automatically, add
init _hp_ignore_sw_impact=1
to your /var/opt/ignite/recovery/latest/system_cfg file, or to the /var/opt/ignite/clients/client/recovery/latest/system_cfg file.
Verifying Recovery Image Results
During a system recovery, Ignite-UX by default restores the system to the state it was in when the recovery image was created. Ignite-UX is a general-purpose installation tool. It modifies many system configuration files if changes from the recovery configuration are required, such as increasing volume sizes.
When you run make_[tapenet]_recovery, system configuration information is gathered and saved in configuration files that are used later when the system is recovered. During the system recovery you are allowed to make changes to this information, and Ignite-UX makes the appropriate changes to the system configuration. If you do not make any changes, Ignite-UX simply reapplies the same information, and there should be no change to the system after recovery.
Most of the system configuration files that Ignite-UX will modify are listed in the script, /opt/ ignite/data/scripts/os_arch_post_l. The os_arch_post_l script checks for the system recovery case by checking the $RECOVERY_MODE variable. When this variable is TRUE, the os_arch_post_l script causes some configuration files to be protected from modification by using the "save_file" function. The os_arch_post_l script uses the "merge_file" function on files that Ignite-UX knows how to merge information into.
The files operated on by "merge_file", as well as those that have a commented out "save_file" line, are likely to be modified by Ignite-UX. Comments in the file explain any exceptions.
Because the list of files modified by Ignite-UX may change from release to release, it is best to look at the os_arch_post_l file on your system to see which files are saved as-is and which are merged with information from the Ignite-UX configuration files.
IMPORTANT: Ignite-UX version C.7.12.519 supports the recovery of a system with APA configured on HP-UX 11i v3 March 2011 update or later. Ignite-UX version C.7.14.264 contains additional fixes for systems with APA configured. HP recommends using Ignite-UX version C.7.14.264 or later when creating recovery archives for systems configured with APA.
For more information about configuring APAs, see APA Administration Guide available at:http:// bizsupport1.austin.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us& taskId=101&prodClassId=-1&contentType=SupportManual&docIndexId=64255& prodTypeId=18964&prodSeriesId=4248623
NOTE: Ignite-UX does support recovery of a system that has all available LAN interfaces configured into aggregate LAN interfaces.
Care should be taken when modifying network information via the Ignite-UX user interface. Without a good understanding of how the aggregate LAN interfaces are setup on a system, modifying network information during a recovery may lead to errors during or after the recovery.
WARNING! Support for APA in Ignite-UX is new and there may be issues discovered with Ignite-UX and APA which are discovered late for inclusion into this manual. Due to this, if you encounter any issues with APA and Ignite-UX, see Ignite-UX Frequently Asked Questions available at:
http://www.hp.com/go/sw-deployment-docs under the FAQ entry titled Does Ignite-UX Support Auto-Port Aggregation (APA)?. The FAQ entry contains information about known problems and information about what is or is not supported when using APA and Ignite-UX.
