make_tape_recovery.1m (2012 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

make_tape_recovery(1M) make_tape_recovery(1M)

NAME

make_tape_recovery - tape based system recovery archive creation

SYNOPSIS

/opt/ignite/bin/make_tape_recovery

[ -s Ignite-UX_server ]

[

-a tape_drive ][-A][

-N][-b][-B boot_destination_ﬁle]

[

-D tape_volume_name]

[ -d tag_string ][-f content_ﬁle][

-i|-ib][-I][-l LLA]

[

-n number_cfg_directories][

-p][-P s|w|e][-m tar|cpio|pax ][-r]

[

-t tape_title_string][

-u][-v

][-x content-options][

XToolkit_Options

][-?]

DESCRIPTION

make_tape_recovery

creates a system recovery archive and stores the archive on a local tape.

make_tape_recovery

is capable of creating system recovery tapes for all tape devices supported by

HP-UX systems. On PA-RISC systems the command has the ability to span multiple tapes. On Integrity

systems all content must ﬁt on one tape. If multiple tapes are needed to create an entire recovery

archive, the make_tape_recovery command must be invoked from a terminal. This is caused by the pax

command failing to prompt for a tape change when invoked from the ignite GUI. The archive created by

make_tape_recovery

is speciﬁc to the system for which it was created and its identity includes host-

name, IP address, networking information, etc. In the event of a root disk failure, the recovery archive

may be installed via tape to restore the system.

The contents of the system recovery archive will always include all ﬁles and directories which are con-

sidered essential for bringing up a functional system. This "essential list" is predeﬁned by

make_tape_recovery

. By running make_tape_recovery in interactive mode, the directories and

ﬁles which make up the "essential list" may be displayed. In addition to the essential list, data may be

included in the archive on a disk/volume group, ﬁle, or directory basis. Nonessential ﬁles and directories

may also be excluded.

Starting with the March 2008 release of HP-UX 11i v3, LVM supports Volume Group Version 2.0. Refer to

lvm(7) for more details on different Volume Group Versions supported by LVM. Please read the

WARN-

INGS section for the limitations and restrictions of this command with regard to supportability of LVM

Volume Groups having Volume Group Versions 2.0 or higher.

HP Serviceguard (SG) introduced Cluster-wide Device Special Files (cDSF) from September 2010 release

of HP-UX 11i v3. Refer to the User Guide of SG for more information on the same. Please refer to

WARN-

INGS section for the limitations and restrictions of this command with regard to supportability of cDSF.

Options

make_tape_recovery

recognizes the following options:

-s Ignite-UX_server

Speciﬁes the hostname of the Ignite-UX server . The conﬁguration ﬁles, defaults and contents

ﬁles for the client system will be written to the Ignite-UX server in

/var/opt/ignite/clients/0xLLA/recovery. The make_tape_recovery

tool

will NFS mount the per-client directory to access this information.

-a tape_drive

Speciﬁes the tape drive device ﬁle that will be used for archiving by make_tape_recovery.

The default is legacy device

/dev/rmt/0mn unless the

/var/opt/ignite/recovery/default ﬁle exists on the system. The tape device ﬁle

must be a no-rewind mode device special ﬁle. On HP-UX 11i v3, when legacy mode devices are

disabled, you can specify the agile device name using the

-a option.

-A Based on the ﬁles that are speciﬁed for inclusion, this option determines which disk(s) and/or

volume group(s) contain those speciﬁed ﬁles, and includes all ﬁles from those disk(s) and/or

volume group(s) in the archive.

-N Indicates no compression for archive. By default, archives are compressed using gzip.

-b When used in combination with the -i option, causes make_tape_recovery to run in the

background after the interactive user interface (UI) completes.

-B boot_destination_file

Speciﬁes the temporary location where the LIF volume will be assembled before it is written

to tape. The default ﬁle is /var/tmp/uxinstlf.recovery for HP9000 systems and

/var/tmp/HPUXIUXLIF for HP Integrity systems. At least 500 MB is required in

HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1

Summary of content (14 pages)

PAGE 1
make_tape_recovery(1M) make_tape_recovery(1M) NAME make_tape_recovery - tape based system recovery archive creation SYNOPSIS /opt/ignite/bin/make_tape_recovery [ -s Ignite-UX_server ] [ -a tape_drive ] [ -A] [ -N] [ -b] [ -B boot_destination_file] [ -D tape_volume_name] [ -d tag_string ] [ -f content_file ] [ -i|-ib] [ -I] [ -l LLA] [ -n number_cfg_directories] [ -p] [ -P s|w|e ] [ -m tar|cpio|pax ] [ -r] [ -t tape_title_string] [ -u] [ -v] [ -x content-options] [ XToolkit_Options] [ -?] DESCRIPTION mak
PAGE 2
make_tape_recovery(1M) make_tape_recovery(1M) /var/tmp directory where the LIF volume will be assembled. The LIF volume and other temporary files required by make_medialif(1M) or make_ipf_tape(1M) will be assembled in the directory specified and then removed after the recovery process completes. -D tape_volume_name Specifies the name of the ANSI tape volume. This option is only for IPF tape. By default, Ignite-UX recovery tool uses the first 6 characters of string HP "month" "day" as tape volume name.
PAGE 3
make_tape_recovery(1M) make_tape_recovery(1M) -P s|w|e When a disk or volume group is partially included in the system recovery archive, generate an ERROR (e), WARNING (w), or SUPPRESS (s) any warning messages that would normally be generated when partial inclusions occur. The default is w, causing WARNING messages to be produced when partial inclusions of disks and/or volume groups are detected.
PAGE 4
make_tape_recovery(1M) make_tape_recovery(1M) are: -bg, -background, -fg, -foreground, -display, -name, -xrm, and synchronous. See the X(1) manual entry for a definition of these options. -? Displays the help screen. Including and Excluding From Archive The contents of the archive may be controlled from the contents file (see -f). The full path for the contents file is /var/opt/ignite/clients/0xLLA /recovery/archive_content on the IgniteUX Server.
PAGE 5
make_tape_recovery(1M) make_tape_recovery(1M) Saving the LIF Area The LIF area of a disk will be archived and restored if it is different from the default LIF area. This means if either the auto-boot line in the AUTO LIF file is not "hpux" or the LIF files in addition to ISL, HPUX, LABEL, and AUTO are present, then the LIF files will be copied to /usr/lib/ignite_bootlif.
PAGE 6
make_tape_recovery(1M) filename INDEX CONFIG IINSTALL IINSTALLFS INSTCMDIA SYSCMDSIA RECCMDSIA SCRIPTS VERSION PAD make_tape_recovery(1M) description Ignite INDEX file (references other config files) Ignite system-specific config file Install kernel Install file system image Archive of commands needed for initial install Archive of commands needed for final install Archive of commands needed for expert recovery Scripts used during install post_load Ignite-UX version used to create tape Additional data to
PAGE 7
make_tape_recovery(1M) make_tape_recovery(1M) Extracting Files from a PA-RISC Recovery After the PA-RISC System Recovery Tape has been created, a single file or files may be extracted from tape by seeking to the tape position where the archive is located. The mt command may be used to seek to the appropriate location, and pax or tar may be used to extract files from the archive.
PAGE 8
make_tape_recovery(1M) make_tape_recovery(1M) Exporting Archive Directory The directory used to store the archives must be exported from the archive server to each client. Exporting the archive directory from the system where the archive will be stored enables make_net_recovery to create and access the archive via NFS.
PAGE 9
make_tape_recovery(1M) make_tape_recovery(1M) environment variables. Help text and some command output not parsed by Ignite-UX will be left in the user’s specified locale. RETURN VALUE make_tape_recovery returns the following values: 0 No warnings or failures occurred; the execution completed successfully. 1 A failure occurred. 2 A warning occurred. EXAMPLES There are two lines for all but the first make_tape_recovery examples given.
PAGE 10
make_tape_recovery(1M) make_tape_recovery(1M) Use the -x option to pass arguments to the print_manifest command. In this example the -d option will be passed so that disk capacity collection via diskinfo is skipped to improve performance. Also the -e option will be passed which causes the output file to be printed with HP-PCL3 control codes for enhanced printer output.
PAGE 11
make_tape_recovery(1M) make_tape_recovery(1M) algorithm for extending logical volumes to ensure success (such as extending contiguous volumes before non-contiguous). An example effect of this is that swap/dump volumes will reside on the root disk ahead of some other volumes even though that may not have been the original layout.
PAGE 12
make_tape_recovery(1M) make_tape_recovery(1M) Data Recovery from Raw Logical Volumes Only file system data is included in recovery archives created by make_tape_recovery. Data included in raw logical volumes (like those that contain database data) is not included in recovery archives, and must be backed up as part of the overall backup stategy of a system. LVM Volume Group Version 2.
PAGE 13
make_tape_recovery(1M) make_tape_recovery(1M) DIAGNOSTICS All major steps within network recovery are logged on the server and displayed via the Ignite-UX Server GUI. FILES make_tape_recovery always stores the archive on the local tape but may store its configuration, log, and status files either locally or on an Ignite-UX server specified by the -s server option. If make_tape_recovery stores its configuration files locally, the directory /var/opt/ignite/recovery is used to store the following files.
PAGE 14
make_tape_recovery(1M) make_tape_recovery(1M) /var/opt/ignite/clients/0xLLA /recovery/date,time /manifest Software and hardware manifest information installed and configured for the system at the time the archive was created. See print_manifest(1M). /var/opt/ignite/clients/0xLLA /recovery/defaults Supplies the default options to make_tape_recovery. Created when run interactively using the -i option or by using the ignite GUI.