Ignite-UX (IUX) Frequently Asked Questions (July 2013)

11.19 Q: Why does the -n option to make_net_recovery not clean up old client
recovery subdirectories?
=============================================================================
==
----------------------------------------
1. Known Problems
----------------------------------------
1.1
Q: I updated my server; now it cannot find "/d_cfg_mnt_sb61/monitor_bpr".
A: This is caused by having a mix of Ignite-UX fileset revisions on your
server. In most cases it happens when you update only one release
bundle (like Ignite-UX-11-23) even though you install other releases
from that server.
An easy way to check for this case is to look at the output from the
command swlist Ignite-UX. All the filesets should have the same
revision; if not, then you need to install all consistent versions.
If you have "boot helper" systems, they also need to have the
Ignite-UX product updated to match the same revision as the server
that they reference.
=============================================================================
==
1.2
Q: Can the Ignite-UX GUI for make_tape_recovery span multiple tapes?
A: No. We use pax as the tool to create the archive tape and there is
no current communication between pax and the GUI to prompt the user
on the GUI when pax requests a second tape. You need to use
make_tape_recovery on the interactively client to be able to span
multiple tapes.
=============================================================================
==
1.3
Q: Why do I get Warnings from pax concerning files that are not on the
client when I run either make_tape_recovery or make_net_recovery?
A: If files are removed from the client between the time the list of files to
be archived is created and the time the files are actually archived,
warnings are generated. For more information, refer to
make_tape_recovery(1M) and make_net_recovery(1M).
=============================================================================
==
1.4
Q: When igniting from an archive, why do I get numerous samreg errors?
A: The problem is that the SAM filesets have not been configured when
certain products are trying to register themselves with SAM.
The workaround is as follows: