Ignite-UX Reference (March 2010, B3921-90005)

make_tape_recovery(1M) make_tape_recovery(1M)
A rewind mode device special file may be used in this case to simplify repeated attempts to list and extract
archive content. Extracting files from tape may take a long time, especially when archives are large.
Extracting Files from an Integrity Recovery Tape
After the Integrity System Recovery Tape has been created, a single file or files may be extracted from tape
by use of the ansitape command. The ansitape command may be used to find the appropriate tape
file and read archive file content. Standard output from this command may be redirected to the pax or
tar command to read archive content and extract files.
To extract a single file from an Integrity recovery archive:
/opt/ignite/lbin/ansitape -xf mt=/dev/rmt/0m archive |.C " tar -xvf -" filena
Extraction of archive content will not start until the ansitape command locates the archive file on tape.
The ansitape command requires use of the f option to request standard output to process archive files
and other files 2 GiB or larger. A rewind mode device special file may be used in this case to simplify
repeated attempts to list and extract archive content. Extracting files from tape may take a long time, espe-
cially when archives are large.
It is possible to extract a single file from an Integrity recovery archive without using the ansitape com-
mand:
mt -t /dev/rmt/0mn rew
mt -t /dev/rmt/0mn fsf 22
tar -xvf /dev/rmt/0m filename
However, use of the ansitape command is recommended in case the format of Integrity recovery tapes
changes in the future.
International Code Set Support
Ignite-UX uses a variety of system commands to accomplish its functionality. Because the output of many
of these commands is parsed, Ignite-UX ensures that the POSIX locale is normally used by modifying envi-
ronment 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. For each of these
examples, the first line assumes that the make_tape_recovery command is being executed on a
stand-alone system, thus not needing the -s server option. The second line assumes the use of a server.
Create a system recovery tape by interacting with the Ignite-UX GUI from the Ignite-UX server:
export DISPLAY=hostname:0
ignite
Create a system recovery tape on the stand-alone system using the standard defaults or from the client,
using settings from the last invocation of the Ignite-UX GUI:
make_tape_recovery
make_tape_recovery -s myserver
Create a system recovery tape with all the files/directories on the disk(s)/volume group(s) containing the
files specified by the default essentials file list /opt/ignite/recovery/mnr_essentials or the
user-defined version of this file, that replaces this file,
/var/opt/ignite/recovery/mnr_essentials:
8