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

=============================================================================
==
4.8
Q: Can you move a volume that was created in a non-root volume to the root
volume during recovery?
A: When you recover a system using a recovery archive, you can extend
the existing logical volume size in the Ignite-UX GUI, "File System"
tab. However, the current tool does not allow you to create a new
logical volume instead of using the old one.
=============================================================================
==
4.9
Q: How can I create empty volume groups during system restoration?
A: When using make_*_recovery tools in an off-site disaster recovery
situation, you may desire to have all the volume groups on the system
recreated during the restore operation even though only the root
volume group data is backed up with make_*_recovery. This may be the
case when you use other tools (such as fbackup/frecover, VERITAS
netbackup, Omniback, etc.) for backing up the non-root data. This
can be accomplished by specifying at least one file in each non-root
volume group to be included in the backup.
The way the make_*_recovery works is that if any files from a volume
group are included, the restoration process will recreate that volume
group during the recovery. So if only one file is specified for
inclusion from the volume group, the entire group will be recreated,
and of course, that one file will be restored.
A more complicated command line would be necessary to accomplish
this, and "-A" would no longer be an option (which is what is used
today).
An example would be:
make_net_recovery -x inc_entire=vg00 \
-x include=/myDataVolume/anyFile ...
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").
=============================================================================
==
4.10
Q: 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?
A: Answer yes to push a shell, then move the file aside to a new name
that will not conflict with any other file name. For example: