X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=man%2Fxml-source%2Famrestore.8.xml;fp=man%2Fxml-source%2Famrestore.8.xml;h=73a266af1b0ca11ef1d8262d8ecbb62dfef78451;hb=538ae376635af705ebcd686f3b4b7b72a6652985;hp=50064fc75cf0daeb85f833bbe3ab596e9611d87d;hpb=11425c69eb58b6103beb68adc13912735ba36975;p=debian%2Famanda
diff --git a/man/xml-source/amrestore.8.xml b/man/xml-source/amrestore.8.xml
index 50064fc..73a266a 100644
--- a/man/xml-source/amrestore.8.xml
+++ b/man/xml-source/amrestore.8.xml
@@ -3,7 +3,7 @@
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"
[
-
+
%global_entities;
]>
@@ -19,333 +19,215 @@
amrestore
-extract backup images from an &A; tape
+low-level data-extraction from Amanda volumes
&author.jds;
&author.sgw.xml;
+&author.dustin;
amrestore
+ --config config-r -c -C
- -bblocksize
- -ffileno
- -l label
+ -b blocksize
+ -f filenum
+ -l label-p-h
- tapedevice|holdingfile
- hostnamedisknamedatestamphostnamedisknamedatestamp...
+ &configoverride.synopsis;
+
+ changerspec
+ --holding
+ holdingfile
+
+
+ hostname
+
+ diskname
+
+ datestamp
+
+ hostname
+
+ diskname
+
+ datestamp
+ ...
+
+
+
+
+
+
-
+Note that this is the only Amanda command which does not take a configuration name as its first argument.
+
+
DESCRIPTION
-Amrestore
-extracts backup images from the tape mounted on
-tapedevice
-or from the holding disk file
-holdingfile
-that match
-hostname,
-diskname
-and
-datestamp
-patterns given on the command line.
-The tape or holding file must be in a format written by the
-amdump
-or
-amflush
-program.
-
-If
-diskname
-is not specified, all backups on the tape for the previous
-hostname
-are candidates.
-If
-datestamp
-is not specified, all backups on the tape for the previous
-hostname
-and
-diskname
-are candidates.
-If no
-hostname,
-diskname
-or
-datestamp
-are specified, every backup on the tape is a candidate.
-
-Hostname
-and
-diskname
-are special expressions described in the "HOST & DISK EXPRESSION" section
-of
-amanda8.
-Datestamp
-are special expression described in the "DATESTAMP EXPRESSION" section
-of
-amanda8.
-For example, if
-diskname
-is "rz[23]a", it would match disks
-rz2a
-and
-rz3a.
-
-Datestamp
-is useful if
-amflush
-writes multiple backup runs to a single tape.
-
-Unless
-
-is used,
-candidate backup images are extracted to files
-in the current directory named:
-
-
-hostname.diskname.datestamp.dumplevel
-
-
-Amrestore doesn't use a changer, it restore from the tape already loaded
-in the
-tapedevice.
-
-OPTIONS
-
-
-
-
-Set the blocksize used to read the tape or holding file.
-All holding files must be read with a blocksize of 32 KBytes.
-Amrestore
-should normally be able to determine the blocksize for tapes
-on its own and not need this parameter.
-
-
-
+Amrestore is a very low-level tool for extracting
+data from Amanda volumes. It does not consult any catalog information or other
+metadata, basing its operations only on the headers found on the volume. This
+makes it an appropriate tool for bare-metal restores of an Amanda server, or
+other situations where the catalog is not available.
+
+See and for higher-level recoveries.
+
+The tool does not reassemble split dumps, but can uncompress compressed
+dumps. Note that decompression may fail for split parts after the first. If
+this occurs, extract the parts without decompressing, concatenate them, and
+decompress the result.
+
+Data is restored from the current volume in
+changerspec, or from the holding file
+holdingfile. In most cases,
+changerspec will name a particular device, e.g.,
+tape:/dev/nst0 or
+s3:mybucket/tape-1.
+
+Only dumps matching the dump specification beginning with
+hostname are extracted. If no specification is
+given, every file on the volume (or the entire holdingfile) is restored. See
+the "DUMP SPECIFICATIONS" section of
+for more information.
+
+Unless is used, candidate backup images are extracted
+to files in the current directory named:
+hostname.diskname.datestamp.dumplevel
-The default is 32 KBytes.
-
-
-
-
-Do a rewind followed by a fsf <fileno> before trying to restore an image.
-
-
-
-
-
-Check if we restoring from the tape with the right
-label
-
-
-
-
-
-Pipe output.
-The first matching backup image is sent to standard output,
-which is normally a pipe to
-restore
-or
-tar,
-then
-amrestore
-quits.
-It may be run again to continue selecting backups to process.
-Make sure you specify the no-rewind
-tapedevice
-when doing this.
-
-
-
+
-Note:
-restore
-may report "short read" errors when reading from a pipe.
-Most versions of
-restore
-support a blocking factor option to let you set the read block size,
-and you should set it to 2.
-See the example below.
-
-
-
-
-Compress output using the fastest method the compression program provides.
-Amrestore
-normally writes output files in a format understood by
-restore
-or
-tar,
-even if the backups on the tape are compressed.
-With the
-
-or
-
-option,
-amrestore
-writes all files in compressed format,
-even if the backups on the tape are not compressed.
-Output file names will have a
-.Z
-or
-.gz
-extension depending on whether
-compress
-or
-gzip
-is the preferred compression program.
-This option is useful when the current directory disk is small.
-
-
-
-
-
-Compress output using the best method the compression program provides
-(may be very CPU intensive).
-See the notes above about the
-
-option.
-
-
-
-
-
-Raw output.
-Backup images are output exactly as they are on the tape,
-including the
-amdump
-headers.
-Output file names will have a
-.RAW
-extension.
-This option is only useful for debugging and other strange circumstances.
-
-
-
-
-
-Header output.
-The tape header block is output at the beginning of each file.
-This is like
-
-except
-
-or
-
-may also be used to compress the result.
-Amrecover
-uses the header to determine the restore program to use.
-
-
-
+OPTIONS
+
+
+
+
+
+Use the given blocksize to read the volume. The default is defined by the
+device.
+
+
+
+
+
+
+Seek to file filenum before beginning the
+restore operation.
+
+
+
+
+
+
+Check that the volume has label label.
+
+
+
+
+
+
+Pipe the first matching file to standard output. This is typically used
+in a shell pipeline to send the data to a process like tar for
+extraction.
+
+
+
+
+
+
+
+If the file is not already compressed, compress it using the fastest
+() or best () compression algorithm.
+Note that amrestore will not re-compress an
+already-compressed file. Without either of these options,
+amrestore will automatically uncompress any compressed
+files. This option is useful when the destination disk is small.
+
+
+
+
+
+
+Include 32k headers on all output files, similar to a holding file. This
+header can be read by another application or utility (see
+Amanda::Header) during the next phase of processing.
+
+
+
+
+
+
+Output raw files. This is similar to , but also
+disables any automatic decompression. Output file names will have a
+.RAW extension.
+
+
+
+ &configoverride.varlistentry;
-If a header is written (-r or -h),
-only 32 KBytes are output regardless of the tape blocksize.
-This makes the resulting image usable as a holding file.
-
-
-
- -oconfigoption
-
-See the "CONFIGURATION OVERRIDE" section in amanda8.
-
- EXAMPLES
+
The following does an interactive restore of disk
-rz3g
-from host
-seine,
-to restore particular files.
-Note the use of the
-b
-option to
-restore,
-which causes it to read in units of two 512-byte blocks (1 Kbyte)
-at a time.
-This helps keep it from complaining about short reads.
-
-
-
-% amrestore -p /dev/nrmt9 seine rz3g | restore -ivbf 2 -
-
+rz3g from host seine, to restore
+particular files. Note the use of the b option to
+restore, which causes it to read in units of two 512-byte
+blocks (1 Kbyte) at a time. This helps keep it from complaining about short
+reads.
+
+
+ amrestore -p /dev/nrmt9 seine rz3g | tar -xv
+The next example extracts all backup images for host
-seine.
-This is the usual way to extract all data for a host after a disk crash.
+seine. This is a typical way to extract all data for a
+host after a disk crash.
-
-
-% amrestore /dev/nrmt9 seine
-
+
+ amrestore /dev/nrmt9 seine
+If the backup datestamp in the above example is
-19910125
-and
-seine
-has level 0 backups of disks
-rz1a
-and
-rz1g
-on the tape,
+20070125 and seine has level 0 backups
+of disks rz1a and rz1g on the tape,
these files will be created in the current directory:
-
-
-seine.rz1a.19910125.0
-seine.rz1g.19910125.0
-
-
-You may also use
-amrestore
-to extract a backup image from a holding disk
-file that has not yet been flushed to tape:
-
-
-
-% amrestore -p /amanda/20001119/seine.rz1a.2 | restore -ivbf 2 -
-
-
-Amrestore
-may be used to generate a listing of images on a tape:
-
-
-
-% mt -f /dev/nrmt9 rewind
-% amrestore -p /dev/nrmt9 no-such-host > /dev/null
-
-
-This asks
-amrestore
-to find images for host
-no-such-host.
-It will not find any entries that match, but along the way will report
-each image it skips.
+
+ seine.rz1a.19910125.0
+ seine.rz1g.19910125.0
+
+
+You may also use amrestore to extract a backup image
+from a holding disk file that has not yet been flushed to tape:
+
+
+ amrestore -p /amanda/20001119/seine.rz1a.2 | tar -xv
+
+
CAVEATS
+
&gnutar; must be used to restore files from backup images created with
-the GNUTAR dumptype.
-Vendor tar programs sometimes fail to read GNU tar images.
-
+the GNUTAR dumptype. Vendor tar programs sometimes fail to read GNU Tar
+images.
-SEE ALSO
-amanda8,
-amdump8,
-amflush8,
-tar1,
-restore8,
-
-
+
+
+,
+,
+,
+
+