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

Omitting the -f <input_file> causes list_expander to use only the
essential files as input. This shows which disks or volume groups
are recreated for the minimal archive.
The following is an example of the output:
In? dsk/vg name minor# Associated disks
-- ------ --------------- ------ -------------------------------
0 d /dev/dsk/c0t3d0
1 v /dev/vg00 0x00 /dev/dsk/c0t6d0 /dev/dsk/c0t4d0
0 v /dev/vg01 0x01 /dev/dsk/c0t1d0
0 v /dev/vg02 0x02 /dev/dsk/c0t2d0
The first column shows, for each disk or volume group, if it will be:
2 = included in full (INC_ENTIRE dsk/vg specified); the disk or
volume group is re-created and files from the archive are
restored
1 = included in part (some files included, some not); the disk or
volume group is re-created and files from the archive are
restored
0 = not included at all (no files from this dsk/vg are included);
the disk or volume group will *NOT* be touched
The second column shows that the client has one whole disk (d) and
three volume groups (v). The third column gives the names of the
disks and volume groups.
=============================================================================
==
11.5
Q: How can I use make_net_recovery if I need to be able to recover from a
tape?
A: There are two ways you can recover from a tape with
make_net_recovery. The following method that you choose depends on
your needs:
- The first method is useful when you want to create a totally
self-contained recovery tape. The tape will be bootable and
contain everything needed to recover your client, including the
archive of your client. During recovery, no access to an Ignite-UX
server is needed.
- The second method is useful when you do not have the ability to
boot the client using the network, but are still able to access the
Ignite-UX server using the network for your archive and
configuration data. This could happen if your client does not
support network boot or if is is not on the same subnet as the
Ignite-UX server. In these cases, use make_boot_tape to create a
bootable tape with just enough information to boot and connect with
the Ignite-UX server. The configuration files and archive are then
retrieved from the Ignite-UX server. For more information, refer
to make_boot_tape(1M).
=============================================================================
==