Ignite-UX Frequently Asked Questions

Guide" at:
http://docs.hp.com/en/IUX/infolib.html
- These manpages are applicable to network recovery are as follows:
* make_net_recovery(4)
* make_boot_tape(1M)
* pkg_rec_depot(1M)
* instl_adm(1M)
* instl_adm(4)
* ignite(5)
- The Ignite-UX Release Notes that detail new features, enhancements
and known problems with the product. It is located in Information
Library and in the /opt/ignite/share/doc/release_note directory.
- The recovery white papers "Successful Cloning using Ignite-UX" and
"Successful System Recovery using Ignite-UX" at:
http://docs.hp.com/en/IUX/infolib.html
===============================================================================
11.2
Q: How can I clone a client using make_net_recovery?
A: The recovery configurations and archives created by make_net_recovery
are stored in a separate directory on the Ignite-UX server for each
client.
Using the configuration and archive created by make_net_recovery on
one client to install a different client involves manually copying
some configuration files, and allowing NFS access to the source
client's archive.
The steps to clone a client using make_net_recovery are as follows:
1. Use make_net_recovery or the Ignite-UX GUI to create a recovery
archive of the source client.
2. Login to the Ignite-UX server.
3. If the client to be installed does not currently have a directory
in /var/opt/ignite/clients on the Ignite-UX server but is up and
running, then use the Ignite-UX GUI to create that directory using
the "Add New Client for Recovery" task.
If the client is not running, you either need to boot the client
from the Ignite-UX server or for a tape made with make_boot_tape
so that this directory is created.
4. Copy the CINDEX file and recovery directory from the source client
to the target client directory. Note that if the client has
previously used make_net_recovery then it already has a CINDEX
file. If a CINDEX file for the target client exists, you may want
to save a copy or hand edit the file to add the desired entries
from the source client.
The following commands copy the required files. You can specify
"src-client" and "client" using either the MAC addresses (for
example, 0x0060B04AAB30) or the client's host name which is
symbolically linked to the MAC address.
# cd /var/opt/ignite/clients/<src-client>
# 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. See exports(4)