Ignite-LUX: Management and Integration of Ignite-UX Software on a Server Running Linux

9
# /opt/ignite/bin/make_net_recovery -s <server> -A
Recovery of the client system is done by reinstalling the client system recovery archive. There is a client-
specific CINDEX file for client-specific recovery archive configuration clauses, so clients do have access to
the recovery archives of other clients.
Saving multiple recovery archives for several systems will require considerable file system space on the
server. A rough estimate for the size of recovery archives is 4GB to 8GB for HP-UX OS content. An Ignite-
UX recovery archive is intended to include only HP-UX OS content and the application programs required to
restore backup content saved using something other than Ignite-UX. Archives might be very large depending
on what is included.
The Ignite-LUX Package Installation and Configuration
The Ignite-LUX package is supplied in the form of a compressed tar archive. This archive includes parts of
the Ignite-UX product typically installed on an HP-UX Ignite-UX server. Most portions of Ignite-UX held on the
HP-UX Ignite-UX server but run on a client system are included in the package and are identical to their
counterparts in the Ignite-LUX product. Almost none of the Ignite-UX product software that normally runs on
an HP-UX Ignite-UX server is included in this package. Those programs would not run correctly on a Linux
system.
Note: This document does not include information about how to obtain the Ignite-LUX package. You should
receive the package as part of the CMS product.
The procedure for installation and configuration of the Ignite-LUX software is significantly different from the
procedure used for an HP-UX server.
Important: If your CMS software installation process performed the Ignite-LUX package installation and
configuration, the steps presented in this section should not be performed. Your CMS software might rely on
a special configuration that differs from the details presented here.
If you must install the Ignite-LUX package yourself, perform the steps presented here to ensure correct Ignite-
UX server operation.
This procedure may be used for initial package installation or to update to a newer version of the package.
When the package is reinstalled to perform an update to a newer version, INDEX, IINSTALLFS config
content, and other normal Ignite-UX server customizations will be preserved.
You must be a privileged user on the Linux server to install the package. The package is provided as a
gzip compressed tar archive. You should consult your OS documentation for details of tar and gzip
command use to unpack a compressed tar archive file.
The archive uses relative file paths. Change your working directory (cd) to the correct directory before
unpacking the archive. The archive is normally unpacked in the root (/) directory. Relative file paths allow
installation to an alternate location if needed for a chroot or other special setup. If the package must be