Ignite-UX Release Notes HP-UX 11iv1, HP-UX 11iv2, and HP-UX 11iv3 (5900-3360, November 2013)

This keyword can be either global or set inside a sw_source. See instl_adm(4) for more
information. If you wish to implicitly select patch bundles, then the sd_software_list
keyword for the patch bundle sw_sel must not be present.
• Patches should be loaded after the software they are patching. To ensure that this is the case,
use the load_order attribute in the sw_source for the patch depot. The default load_order
is zero (0) for core software and five (5) for applications. Make the load_order greater
than five (5) for a patch depot to force it to be installed last.
make_[tape|net]_recovery issues
• There are some special issues when using Ignite-UX in a mirror disk environment. See the white
paper at: http://www.hp.com/go/ignite-ux.
• When a system has a DCE/DFS file system, the system recovery archive will not include
aggregate file systems which have been created. These file systems must be manually restored.
• When make_net_recovery runs, it checks to make sure there is enough disk space available
for the archive being created. However, if multiple make_net_recovery sessions are
creating archives on the same server at the same time, it is possible to run out of disk space.
• When the client machine is on a different network domain than the Ignite-UX server, the
recovery GUI may have difficulty finding the client. This problem can be remedied by making
sure that both the client and server have DNS search strings for both of the domains.
• make_net_recovery has not been tested in ServiceGuard environments.
• When make_net_recovery archives a system that contains direct automounts, it can produce
the error:
pax: dcatmp : Permission denied
dcatmp> 2 GB. Not Dumped.
The automount is (correctly) not archived, and the error can be safely ignored.
• Both make_net_recovery and make_tape_recovery may result in a warning message
regarding temporary files that pax was not able to put into the archive, such as:
◦ Archiving contents of XX via tar image to local device/dev/rmt/0mn.
pax: var/stm/logs/tools/10_0_15_0_6/id : No such file or directory
WARNING! The pax command returned a non-zero exit status (exit status 1)
This is because there is a window of opportunity when Ignite-UX checks to see if a file
still exists and when pax attempts to place the file into the archive. It is uncommon but
still possible to see these messages.
• Due to changes in the essential files processing in list_expander, directory structures may
be only partially included in the recovery archive. This may occur under some circumstances
when either the -A or -x inc_entire options are used with symlinks in essential directories
pointing to files outside of the essential directories. This problem is expected to be addressed
in a future release of Ignite-UX.
• make_tape_recovery is the same code as make_net_recovery, thus most of the known
issues apply to both commands.
36 Known problems and workarounds