1AMFETCHDUMP(8) AMFETCHDUMP(8)
2
6 amfetchdump - extract backup images from multiple Amanda tapes.
7
9 amfetchdump [-pcClawns] [-d device] [-O directory] [-i logfile]
10 [-b blocksize] config hostname
11 [disk [ date [ level [ hostname [...] ] ] ]]
12 [-o configoption]...
13
15 Amfetchdump pulls one or more matching dumps from tape or from the
16 holding disk, handling the reassembly of multi-tape split dump files as
17 well as any tape autochanger operations.
18 It will automatically use the logs created by amdump(8) to locate
20 available dumps on tape, in the same way that the find feature of
21 amadmin(8) lists available dumps. If these logs are unavailable, it can
22 search tape-by-tape to find what it needs, and can generate new logs to
23 serve as an emergency tape inventory.
24 The hostname, diskname, datestamp, and level dump pattern-matching
26 works as in amrestore(8), with the added requirement that at minimum a
27 hostname must be specified when not in inventory mode.
28 Unless -p is used, backup images are extracted to files in the current
30 directory named:
31 hostname.diskname.datestamp.dumplevel
33
35 -p
36 Pipe exactly one complete dump file to stdout, instead of writing
37 the file to disk. This will restore only the first matching
38 dumpfile (where "first" is determined by the dump log search
39 facility).
40 -d device
42 Restore from this tape device instead of the default.
43 -O directory
45 Output restored files to this directory, instead of to the current
46 working directory.
47 -c
49 Compress output, fastest method available.
50 -C
52 Compress output, smallest file size method available.
53 -l
55 Leave dumps in the compressed/uncompressed state in which they were
56 found on tape. By default, amfetchdump will automatically
57 uncompress when restoring.
58 -a
60 Assume that all tapes are already available, via tape changer or
61 otherwise, instead of prompting the operator to ensure that all
62 tapes are loaded.
63 -i filename
65 Generate an inventory of all dumps "seen" on the tapes we search,
66 for later use as a log.
67 -w
69 Wait to put split dumps together until all chunks have been
70 restored. Normally, amfetchdump will attempt to read pieces of a
71 split file from tape in order, so that it can assemble them simply
72 by appending each file to the first. This option disables the
73 appending behavior, and instead restores each piece as an
74 individual file and reassembles them only after all have been
75 restored.
76 Note
78 This requires at least double the size of your dump in free disk
79 space, in order to build the final assembled dumpfile.
80 This behavior is implicitly invoked in circumstances where knowing
82 the location of all dumps on tape in advance is not possible, such
83 as when you are restoring without log files.
84 -n
86 Do not reassemble split dump files at all, just restore each piece
87 as an individual file.
88 -s
90 Do not fast-forward straight to needed files on tape. This will
91 slow down most restores substantially. Only use this option if your
92 tape drive does not properly support the fast-forward operation.
93 -b blocksize
95 Force a particular block size when reading from tapes. This value
96 will usually be autodetected, and should not normally need to be
97 set.
98 -o configoption
100 See the "CONFIGURATION OVERWRITE" section in amanda(8).
101
103 All the examples here assume your configuration is called SetA.
104 Here's a simple case, restoring all known dumps of the host vanya to
106 the current working directory.
107 $ amfetchdump SetA vanya
109 A more likely scenario involves restoring a particular dump from a
112 particular date. We'll pipe this one to GNU-tar as well, to
113 automatically extract the dump.
114 $ amfetchdump -p SetA vanya /home 20051020 | gtar -xvpf -
116 In a situation where all of our dump logs have been wiped out, we could
119 also use amfetchdump to inventory our tapes and recreate an imitation
120 of those logs, which we'll send to stdout for casual perusal.
121 $ amfetchdump -i - SetA
124 Note that you can specify a restore while in inventory mode, and
128 amfetchdump will continue searching for more dumps from this host even
129 after successfully restoring a dump, inventorying all the while. If
130 your backup searcher has been trashed, this is a handy way to recover
131 what you have.
132 $ amfetchdump -i /var/amanda/log SetA backupserver
135
139 Amfetchdump is dependent on accessing your server's config, tape
140 changer, and (normally) dump logs. As such, it's not necessarily the
141 most useful tool when those have all been wiped out and you desperately
142 need to pull things from your tape. Pains have been taken to make it as
143 capable as possible, but for seriously minimialist restores, look to
144 amrestore(8) or dd(8) instead.
145
147 John Stange, <building@nap.edu>, National Academies Press
148 Ian Turner, <ian@zmanda.com>: XML-conversion
150
152 amanda(8), amadmin(8), amrestore(8), tar(1) restore(8)
153 02/07/2007 AMFETCHDUMP(8)