amfetchdump - extract backup images from multiple Amanda tapes.
amfetchdump [-phcClawns] [-d device] [-O directory] [-b blocksize]
[--header-fd fd] [--header-file filename]
[-o configoption]... config hostname
[disk [ date [ level [ hostname [...] ] ] ]]
Amfetchdump pulls one or more matching dumps from tape or from the
holding disk, handling the reassembly of multi-tape split dump files as
well as any tape autochanger operations.
It will automatically use the logs created by amdump(8) to locate
available dumps on tape, in the same way that the find feature of
amadmin(8) lists available dumps. If these logs are unavailable, it can
search tape-by-tape to find what it needs, and can generate new logs to
serve as an emergency tape inventory.
The hostname, diskname, datestamp, and level dump pattern-matching
works as in amrestore(8), with the added requirement that at minimum a
hostname must be specified when not in inventory mode.
Unless -p is used, backup images are extracted to files in the current
If a changer error occurs, or the -d option is given, then amfetchdump
prompts for each required volume.
Pipe exactly one complete dump file to stdout, instead of writing
the file to disk. This will restore only the first matching
dumpfile (where "first" is determined by the dump log search
Output the amanda header as a 32K block to same output as the
Output the amanda header to the numbered file descriptor.
Output the amanda header to the filename.
Restore from this device or changer instead of the default,
prompting for each volume.
Output restored files to this directory, instead of to the current
Compress output, fastest method available.
Compress output, smallest file size method available.
Leave dumps in the compressed/uncompressed state in which they were
found on tape. By default, amfetchdump will automatically
uncompress when restoring.
Assume that all tapes are already available, via tape changer or
otherwise, instead of prompting the operator to ensure that all
tapes are loaded.
Do not reassemble split dump files at all, just restore each piece
as an individual file.
See the "CONFIGURATION OVERRIDE" section in amanda(8).
All the examples here assume your configuration is called SetA.
Here´s a simple case, restoring all known dumps of the host vanya to
the current working directory.
$ amfetchdump SetA vanya
A more likely scenario involves restoring a particular dump from a
particular date. We´ll pipe this one to GNU-tar as well, to
automatically extract the dump.
$ amfetchdump -p SetA vanya /home 20051020 | gtar -xvpf -
Amfetchdump is dependent on accessing your server´s config, tape
changer, and (normally) dump logs. As such, it´s not necessarily the
most useful tool when those have all been wiped out and you desperately
need to pull things from your tape. Pains have been taken to make it as
capable as possible, but for seriously minimialist restores, look to
amrestore(8) or dd(8) instead.
amanda(8), amadmin(8), amrestore(8), tar(1), restore(8)
The Amanda Wiki: : http://wiki.zmanda.com/
John Stange <email@example.com>
National Academies Press
Ian Turner <firstname.lastname@example.org>
Zmanda, Inc. (http://www.zmanda.com)