Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

to install it from an LIF. The above errors are the result of the bootloader attempting to read the
kernel from an HFS file system, which is not possible on a tape.
Older releases of the bootloader prepended a colon (:) to the VINSTALL kernel name. This provision
is unavailable from the bootloader for 11i v1. In this case, the correct boot string would be:
bo 4/2/0.1.0 :VINSTALL
Not:
bo 4/2/0.1.0 VINSTALL
For machines other than the V-class, always use: INSTALL to represent the installation kernel when
manually booting from tape or an installation CD. The bootloader automatically changes it to
:VINSTALL on systems that require a 64 bit kernel for installation.
How do I include all volume/disk groups into a recovery tape?
To include all volume and disk groups on the system into a recovery tape (can be used with
make_net_recovery as well) use the following command:
# make_tape_recovery -A -x inc_cross=/
The make_tape_recovery manual page defines inc_cross as follows:
-x inc_cross=file|dir
Includes the file or directory in the recovery archive and crosses mount points to access any
directories that are mounted or files contained in directories that are mounted.
Are multi-byte characters supported in file names in Ignite-UX?
Currently, multi-byte characters are not supported in file names.
Can you move a volume that was created in a non-root volume to the root volume
during recovery?
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.
How can I create empty volume groups during system restoration?
When using make_*_recovery tools in an off-site disaster recovery situation, you may want 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 might be the case when
you use other tools (such as fbackup/frecover, VERITAS netbackup, Omniback, and so
on.) 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.
If any file is included in make_*_recovery command from a volume group, the restoration
process will recreate that volume group during the recovery. Hence, if only one file is specified for
inclusion from the volume group, the entire group will be recreated, and that specific 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 currently used).
An example would be:
make_net_recovery -x inc_entire=vg00 \
-x include=/myDataVolume/anyFile ...
Frequently asked questions 23