HP-UX HB v13.00 Ch-06 - Ignite-UX

HP-UX Handbook – Rev 13.00 Page 23 (of 58)
Chapter 06 Ignite-UX
October 29, 2013
Ignite-UX System Recovery Tools - make_recovery
The make_recovery command has been obsolete for some time, but was shipped with Ignite-
UX along with its replacements command make_tape_recovery. Executing make_recovery
prompted a note saying:
NOTE: make_recovery(103): The make_recovery command will be replaced by
make_tape_recovery. Both commands are supported in this release
(Ignite-UX Revision 3.2). Please read the man page
make_tape_recovery(1M) for usage of the new command. In a
future release, make_recovery will be replaced by a script that
calls make_tape_recovery.
With Ignite-UX version C.6.0.x the make_recovery command was dropped completely and is
not available.
Be aware that options used with make_recovery are not identical with the same options used
with make_tape_recovery. Example: the “–A” option has different meanings for
make_recovery and make_tape_recovery. By default ‘make_recovery –A’ archived the
complete root volume group, whereas ‘make_tape_recovery -A’ will only include “essential”
files and directories.
Ignite-UX System Recovery Tools - make_tape_recovery
Overview
 Can be executed locally (also using a Terminal User Interface) as well as from the
Ignite-UX server.
 Creates a bootable DDS/DLT tape. It can also span multiple tapes if run locally.
 Besides the root volume group, other volume groups can be archived as well. Note:
This is not recommended, because Ignite-UX is not a backup tool and will greatly
increase recovery time as well as over-write possibly newer data files. Backup data
with proper backup utilities such as fbackup, pax, tar, etc.
 The client specific configuration files are either stored locally or on the Ignite-UX
server.
 Replaces make_recovery since Ignite-UX versions A.3.2/B.3.2.
Creating a make_tape_recovery Tape - Ignite-UX Server GUI
On your host system, allow the Ignite-UX server to access the display with:
# xhost +<Ignite_server_name>