3 .\" Author: James da Silva <jds@amanda.org>
4 .\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
6 .\" Manual: System Administration Commands
7 .\" Source: Amanda 3.3.3
10 .TH "AMRESTORE" "8" "01/10/2013" "Amanda 3\&.3\&.3" "System Administration Commands"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 amrestore \- low\-level data\-extraction from Amanda volumes
33 .HP \w'\fBamrestore\fR\ 'u
34 \fBamrestore\fR [\-\-config\ \fIconfig\fR] [\-r | \-c | \-C] [\-b\ \fIblocksize\fR] [\-f\ \fIfilenum\fR] [\-l\ \fIlabel\fR] [\-p] [\-h] [\-\-exact\-match] [\fB\-o\fR\ \fIconfigoption\fR...] [{\fIchangerspec\fR} | {[\-\-holding]\ \fIholdingfile\fR}] [\fIhostname\fR\ [\ \fIdiskname\fR\ [\ \fIdatestamp\fR\ [\ \fIhostname\fR\ [\ \fIdiskname\fR\ [\ \fIdatestamp\fR\ \&.\&.\&.\ ]\ ]\ ]\ ]\ ]]
36 Note that this is the only Amanda command which does not take a configuration name as its first argument\&.
40 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\&.
46 for higher\-level recoveries\&.
48 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\&.
50 Data is restored from the current volume in
51 \fIchangerspec\fR, or from the holding file
52 \fIholdingfile\fR\&. In most cases,
54 will name a particular device, e\&.g\&.,
57 s3:mybucket/tape\-1\&.
59 Only dumps matching the dump specification beginning with
61 are extracted\&. If no specification is given, every file on the volume (or the entire holdingfile) is restored\&. See the "DUMP SPECIFICATIONS" section of
63 for more information\&.
67 is used, candidate backup images are extracted to files in the current directory named:
68 hostname\&.diskname\&.datestamp\&.dumplevel
71 \fB\-b \fR\fB\fIblocksize\fR\fR
73 Use the given blocksize to read the volume\&. The default is defined by the device\&.
76 \fB\-f \fR\fB\fIfilenum\fR\fR
80 before beginning the restore operation\&.
83 \fB\-l \fR\fB\fIlabel\fR\fR
85 Check that the volume has label
91 Pipe the first matching file to standard output\&. This is typically used in a shell pipeline to send the data to a process like
98 If the file is not already compressed, compress it using the fastest (\fB\-c\fR) or best (\fB\-C\fR) compression algorithm\&. Note that
100 will not re\-compress an already\-compressed file\&. Without either of these options,
102 will automatically uncompress any compressed files\&. This option is useful when the destination disk is small\&.
107 Include 32k headers on all output files, similar to a holding file\&. This header can be read by another application or utility (see
108 \fBAmanda::Header\fR) during the next phase of processing\&.
113 Output raw files\&. This is similar to
114 \fB\-h\fR, but also disables any automatic decompression\&. Output file names will have a
119 \fB\-\-exact\-match\fR
121 The host and disk are parsed as exact values
124 \fB\-o \fR\fB\fIconfigoption\fR\fR
126 See the "CONFIGURATION OVERRIDE" section in
131 The following does an interactive restore of disk
134 \fIseine\fR, to restore particular files\&. Note the use of the
137 \fIrestore\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\&.
139 amrestore \-p /dev/nrmt9 seine rz3g | tar \-xv
142 The next example extracts all backup images for host
143 \fIseine\fR\&. This is a typical way to extract all data for a host after a disk crash\&.
145 amrestore /dev/nrmt9 seine
148 If the backup datestamp in the above example is
152 has level 0 backups of disks
156 on the tape, these files will be created in the current directory:
158 seine\&.rz1a\&.19910125\&.0
159 seine\&.rz1g\&.19910125\&.0
164 to extract a backup image from a holding disk file that has not yet been flushed to tape:
166 amrestore \-p /amanda/20001119/seine\&.rz1a\&.2 | tar \-xv
171 must be used to restore files from backup images created with the GNUTAR dumptype\&. Vendor tar programs sometimes fail to read GNU Tar images\&.
175 \fBamanda-match\fR(7),
176 \fBamfetchdump\fR(8),
180 : http://wiki.zmanda.com/
183 \fBJames da Silva\fR <\&jds@amanda\&.org\&>
185 \fBStefan G\&. Weichinger\fR <\&sgw@amanda\&.org\&>
187 \fBDustin J\&. Mitchell\fR <\&dustin@zmanda\&.com\&>
189 Zmanda, Inc\&. (http://www\&.zmanda\&.com)