3 Prev Chapter 36. The Amanda Manual Pages. Next
5 -------------------------------------------------------------------------------
9 amfetchdump
\14 extract backup images from multiple Amanda tapes.
13 amfetchdump [-pcClawns] [-d device] [-O directory] [-i logfile] [-b blocksize]
14 config hostname [ disk [ date [ level [ hostname [...] ] ] ] ] [ -
19 Amfetchdump pulls one or more matching dumps from tape or from the holding
20 disk, handling the reassembly of multi-tape split dump files as well as any
21 tape autochanger operations.
22 It will automatically use the logs created by amdump(8) to locate available
23 dumps on tape, in the same way that the find feature of amadmin(8) lists
24 available dumps. If these logs are unavailable, it can search tape-by-tape to
25 find what it needs, and can generate new logs to serve as an emergency tape
27 The hostname, diskname, datestamp, and level dump pattern-matching works as in
28 amrestore(8), with the added requirement that at minimum a hostname must be
29 specified when not in inventory mode.
30 Unless -p is used, backup images are extracted to files in the current
32 hostname.diskname.datestamp.dumplevel
39 Pipe exactly one complete dump file to stdout, instead of writing the
40 file to disk. This will restore only the first matching dumpfile (where
41 "first" is determined by the dump log search facility).
44 Restore from this tape device instead of the default.
47 Output restored files to this directory, instead of to the current
51 Compress output, fastest method available.
54 Compress output, smallest file size method available.
57 Leave dumps in the compressed/uncompressed state in which they were found
58 on tape. By default, amfetchdump will automatically uncompress when
62 Assume that all tapes are already available, via tape changer or
63 otherwise, instead of prompting the operator to ensure that all tapes are
67 Generate an inventory of all dumps "seen" on the tapes we search, for
71 Wait to put split dumps together until all chunks have been restored.
72 Normally, amfetchdump will attempt to read pieces of a split file from
73 tape in order, so that it can assemble them simply by appending each file
74 to the first. This option disables the appending behavior, and instead
75 restores each piece as an individual file and reassembles them only after
76 all have been restored.
80 This requires at least double the size of your dump in free disk space,
81 in order to build the final assembled dumpfile.
82 This behavior is implicitly invoked in circumstances where knowing the
83 location of all dumps on tape in advance is not possible, such as when
84 you are restoring without log files.
87 Do not reassemble split dump files at all, just restore each piece as an
91 Do not fast-forward straight to needed files on tape. This will slow down
92 most restores substantially. Only use this option if your tape drive does
93 not properly support the fast-forward operation.
96 Force a particular block size when reading from tapes. This value will
97 usually be autodetected, and should not normally need to be set.
100 See the "CONFIGURATION OVERRIDE" section in amanda(8).
105 All the examples here assume your configuration is called SetA.
106 Here's a simple case, restoring all known dumps of the host vanya to the
107 current working directory.
109 $ amfetchdump SetA vanya
110 A more likely scenario involves restoring a particular dump from a particular
111 date. We'll pipe this one to GNU-tar as well, to automatically extract the
114 $ amfetchdump -p SetA vanya /home 20051020 | gtar -xvpf -
115 In a situation where all of our dump logs have been wiped out, we could also
116 use amfetchdump to inventory our tapes and recreate an imitation of those logs,
117 which we'll send to stdout for casual perusal.
119 $ amfetchdump -i - SetA
120 Note that you can specify a restore while in inventory mode, and amfetchdump
121 will continue searching for more dumps from this host even after successfully
122 restoring a dump, inventorying all the while. If your backup searcher has been
123 trashed, this is a handy way to recover what you have.
125 $ amfetchdump -i /var/amanda/log SetA backupserver
129 Amfetchdump is dependent on accessing your server's config, tape changer, and
130 (normally) dump logs. As such, it's not necessarily the most useful tool when
131 those have all been wiped out and you desperately need to pull things from your
132 tape. Pains have been taken to make it as capable as possible, but for
133 seriously minimialist restores, look to amrestore(8) or dd(8) instead.
137 John Stange, <building@nap.edu>, National Academies Press
138 Ian Turner, <ian@zmanda.com>: XML-conversion
142 amanda(8), amadmin(8), amrestore(8), tar(1) restore(8)
143 -------------------------------------------------------------------------------