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

# find CINDEX recovery | cpio -pdvma ../<target-client>
5. Give the target client NFS access to the archive of the source client by logging into the Ignite-UX
server that holds the archive. Typically, each client has its own directory for storing the archives,
and the directory is exported only to the individual client. For Ignite-UX servers running releases
prior to 11.31, you must edit the /etc/exports file to allow access to both the source and
target clients as follows:
# vi /etc/exports
(append ":target" to the end of the source client's line)
# exportfs -av
where :target is the hostname of the target system. For more information, see exports(4).
For Ignite-UX servers running 11.31 or later, you must edit the /etc/dfs/dfstab file to
allow access to both the source and target clients as follows:
# vi /etc/dfs/dfstab
(append ",ro=target" to the -o argument of the source
client's line)
# shareall -F nfs
where target is a fully qualified client name. Since this client will not be creating an archive,
the client will not have write access to the archive directory. For more information, see dfstab(4).
6. Now, boot the client from the Ignite-UX server using any method. When you install the client,
you can select from the recovery configurations of the source client.
How can I tell which files will be included in the archive created by
make_net_recovery?
Execute /opt/ignite/lbin/list_expander as described in the next FAQ question, replacing
the -d option (which lists the disks and/or volume groups) with the -l option (which lists the
individual directories and files that will be included in the archive).
How can I tell which disks or volume groups get recreated during an installation from
a make_net_recovery configuration?
Execute the following from the client:
# /opt/ignite/lbin/list_expander -d -f <input_file>
where: <input_file> specifies what is to be archived. For more information about format of
<input_file>, see make_net_recovery(4). The make_net_recovery command can take input
from an input file, no input, or input from the command line with the x option. The list_expander
command can take input from an input file, or no input, but does not have an x option like
make_net_recovery. To see the result of using x options, put the options in a file and
passlist_expander as the file name.
If you used the Ignite-UX GUI to specify what is to be included in the archive, then the input file
can be found on the Ignite-UX server in:
# /var/opt/ignite/clients/<client>/recovery/archive_content
You can copy this file from the server to the client, then run list_expander against that file.
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:
Frequently asked questions 43