Successful System Recovery using Ignite-UX

Abstract
Ignite-UX for HP-UX addresses the need for system administrators to perform operating system
installations, deployment, and recovery, often on a large scale. It provides the means for creating
and reusing standard operating system configurations. Additionally, Ignite-UX delivers the ability to
archive operating system configurations and to use these archives to replicate systems, with the
added benefit of speeding up the process. Ignite-UX also permits various customizations, and is
capable of both interactive and unattended operating modes.
Executive summary
As a systems administrator developing a disaster recovery strategy, you have to determine how
often recovery archives should be created, how long to retain them, and what media is most
appropriate: tape (using make_tape_recovery) or network (using make_net_recovery).
Unfortunately, these decisions are not straightforward and you must consider a variety of issues
unique to your environment and circumstances.
The information contained in this white paper is intended to aid you in developing a recovery
archive strategy. The issues discussed are related so you should read the document in its entirety
before coming to any decision. You then need to determine the greatest impacts on a system-by-
system (or application-by-application) basis and use that to shape your strategy.
Recovery archive creation considerations
Typically, a recovery archive is created when the system is quiescent and can be executed in
single-user mode. This is, however, not a requirement of Ignite-UX, but rather, the choice of the
system administrator. In addition, the creation of a recovery archive depends on how it is
integrated into your backup strategy.
For more information on how to create recovery archives in single-user mode, refer to
make_tape_recovery(1M) and make_net_recovery(1M).
CAUTION:
HP does not recommend the use of any component of Ignite-UX as part
of any backup strategy. The Ignite-UX product is not an enterprise
backup utility and therefore does not provide any of the features
associated with Enterprise Backup and Recovery utilities such as HP
StorageWorks Data Protector (for example, the recovery of individual
files).
Ignite-UX is intended for the cloning, recovery, and installation of systems only. Because recovery
archives can be created when applications are executing, any application data
1
included in a
recovery archive should be treated with suspicion as it could be inconsistent.
1
The term "application data" is used extensively in this white paper. In this context, it means all files (special or regular) and their contents,
directories, permissions, access control lists, and data contained within raw devices (if used) that are used by the system. In other words, all
files not associated with the HP-UX operating system are considered application data.
2