3 .\" Author: James da Silva <jds@amanda.org>
4 .\" Generator: DocBook XSL Stylesheets vsnapshot_8273 <http://docbook.sf.net/>
6 .\" Manual: System Administration Commands
7 .\" Source: Amanda 2.6.1p1
10 .TH "AMRESTORE" "8" "04/10/2009" "Amanda 2\&.6\&.1p1" "System Administration Commands"
11 .\" -----------------------------------------------------------------
12 .\" * set default formatting
13 .\" -----------------------------------------------------------------
14 .\" disable hyphenation
16 .\" disable justification (adjust text to left margin only)
18 .\" -----------------------------------------------------------------
19 .\" * MAIN CONTENT STARTS HERE *
20 .\" -----------------------------------------------------------------
22 amrestore \- extract backup images from an \fIAmanda\fR tape
24 .HP \w'\fBamrestore\fR\ 'u
25 \fBamrestore\fR [\-r | \-c | \-C] [\-b | \fIblocksize\fR] [\-f | \fIfileno\fR] [\-l | \fIlabel\fR] [\-p] [\-h] \fItapedevice\fR|\ \fIholdingfile\fR [\fIhostname\fR [\fIdiskname\fR [\fIdatestamp\fR [\fIhostname\fR [\fIdiskname\fR [\fIdatestamp\fR | \&.\&.\&.]]]]]]
29 extracts backup images from the tape mounted on
31 or from the holding disk file
38 patterns given on the command line\&. The tape or holding file must be in a format written by the
46 is not specified, all backups on the tape for the previous
50 is not specified, all backups on the tape for the previous
54 are candidates\&. If no
59 are specified, every backup on the tape is a candidate\&.
64 are special expressions described in the "HOST & DISK EXPRESSION" section of
67 are special expression described in the "DATESTAMP EXPRESSION" section of
68 \fBamanda\fR(8)\&. For example, if
70 is "rz[23]a", it would match disks
78 writes multiple backup runs to a single tape\&.
82 is used, candidate backup images are extracted to files in the current directory named:
84 \fIhostname\&.diskname\&.datestamp\&.dumplevel\fR
86 Amrestore doesn\'t use a changer, it restore from the tape already loaded in the
92 Set the blocksize used to read the tape or holding file\&. All holding files must be read with a blocksize of 32 KBytes\&.
94 should normally be able to determine the blocksize for tapes on its own and not need this parameter\&.
97 The default is 32 KBytes\&.
101 Do a rewind followed by a fsf <fileno> before trying to restore an image\&.
106 Check if we restoring from the tape with the right
112 Pipe output\&. The first matching backup image is sent to standard output, which is normally a pipe to
117 quits\&. It may be run again to continue selecting backups to process\&. Make sure you specify the no\-rewind
124 may report "short read" errors when reading from a pipe\&. Most versions of
126 support a blocking factor option to let you set the read block size, and you should set it to 2\&. See the example below\&.
130 Compress output using the fastest method the compression program provides\&.
132 normally writes output files in a format understood by
135 \fBtar\fR, even if the backups on the tape are compressed\&. With the
141 writes all files in compressed format, even if the backups on the tape are not compressed\&. Output file names will have a
145 extension depending on whether
149 is the preferred compression program\&. This option is useful when the current directory disk is small\&.
154 Compress output using the best method the compression program provides (may be very CPU intensive)\&. See the notes above about the
161 Raw output\&. Backup images are output exactly as they are on the tape, including the
163 headers\&. Output file names will have a
165 extension\&. This option is only useful for debugging and other strange circumstances\&.
170 Header output\&. The tape header block is output at the beginning of each file\&. This is like
176 may also be used to compress the result\&.
178 uses the header to determine the restore program to use\&.
181 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\&.
183 \fB\-o\fR \fIconfigoption\fR
185 See the "\fBCONFIGURATION OVERRIDE\fR" section in
190 The following does an interactive restore of disk
193 \fIseine\fR, to restore particular files\&. Note the use of the
196 \fBrestore\fR, 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\&.
202 % amrestore \-p /dev/nrmt9 seine rz3g | restore \-ivbf 2 \-
208 The next example extracts all backup images for host
209 \fIseine\fR\&. This is the usual way to extract all data for a host after a disk crash\&.
215 % amrestore /dev/nrmt9 seine
221 If the backup datestamp in the above example is
225 has level 0 backups of disks
229 on the tape, these files will be created in the current directory:
235 seine\&.rz1a\&.19910125\&.0
236 seine\&.rz1g\&.19910125\&.0
244 to extract a backup image from a holding disk file that has not yet been flushed to tape:
250 % amrestore \-p /amanda/20001119/seine\&.rz1a\&.2 | restore \-ivbf 2 \-
257 may be used to generate a listing of images on a tape:
263 % mt \-f /dev/nrmt9 rewind
264 % amrestore \-p /dev/nrmt9 no\-such\-host > /dev/null
272 to find images for host
273 \fBno\-such\-host\fR\&. It will not find any entries that match, but along the way will report each image it skips\&.
277 must be used to restore files from backup images created with the GNUTAR dumptype\&. Vendor tar programs sometimes fail to read GNU tar images\&.
285 : http://wiki.zmanda.com
288 \fBJames da Silva\fR <\&jds@amanda\&.org\&>
290 \fBStefan G\&. Weichinger\fR <\&sgw@amanda\&.org\&>