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

Table 1 Output
Associated disksminor#namedsk/vgIn?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __ _ _ _ _ _ _ _ __ _ _ _ _ _ _ _ __ _ _ _ _ _ _ __ _ _ _ _ _ _
_
/dev/dsk/c0t3d0d0
/dev/dsk/c0t6d0 /dev/dsk/c0t4d00x00/dev/vg00v1
/dev/dsk/c0t1d00x01/dev/vg01v0
/dev/dsk/c0t2d00x02/dev/vg02v0
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 is not
included
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.
How can I use make_net_recovery, if I need to be able to recover from a tape?
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 contains 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 the client is not able to boot over the network, but are still
able to access the Ignite-UX server using the network for your archive and configuration data.
This might happen if your client does not support network boot or if 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, see
make_boot_tape(1M).
Which files does Ignite-UX change during an installation from a
make_net_recovery configuration?
During a client recovery, Ignite-UX strives to restore the client back to the way it was. However,
Ignite-UX is a general purpose installation tool and as such it has the capabilities of modifying
many client configuration files.
When you run make_net_recovery, client configuration information is gathered and saved in
configuration files that are used later when the client is recovered. During the client recovery, you
are allowed to make changes to this information, then Ignite-UX makes the appropriate changes
to the client configuration. If you do not make any changes, then Ignite-UX simply reapplies the
last installation information and makes no changes to the client's configuration.
Most of the client configuration files that Ignite-UX modifies are listed in the script:
/opt/ignite/data/scripts/os_arch_post_l.
The os_arch_post_l script checks for the client recovery case by checking the $RECOVERY_MODE
variable. When this variable is true, the os_arch_post_l script causes some configuration files
44 Network recovery