amfetchdump (8) - Linux Man Pages
amfetchdump: extract backup images from multiple Amanda tapes.
amfetchdump - extract backup images from multiple Amanda tapes.
amfetchdump [-c | -C | -l] [-p | -n] [-a] [-O
directory] [-d device] [-h | --header-file filename | --header-fd fd] [--decompress | --no-decompress | --server-decompress | --client-decompress] [--extract --directory directory [--data-path amanda|directtcp] [--application-property NAME=VALUE]*] [--decrypt | --no-decrypt | --server-decrypt | --client-decrypt] [--exact_match] [-o configoption...] config hostname [disk [ date [ level [ hostname [...] ] ] ]]
It will automatically use the Amanda catalog to locate available dumps on tape, in the same way that the find feature of amadmin(8) lists available dumps.
The hostname, diskname, datestamp, and level dump specifications are further described in amanda-match(7). Note that at minimum a hostname must be specified.
Unless -p is used, backup images are extracted to files in the current directory named:
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 facility).
- Output the amanda header as a 32K block to same output as the image.
- 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 working directory.
- Compress output, fastest method available.
- Compress output, smallest file size method available.
- Always do the decompression, this is the default.
- Never do the decompression.
- Do the decompression only if the compression was done on the server.
- Do the decompression only if the compression was done on the client.
- Always do the decryption, this is the default.
- Never do the decryption.
- Do the decryption only if the encryption was done on the server.
- Do the decryption only if the encryption was done on the client.
- The host and disk are parsed as exact values
- Extract the backup on the server in the directory directory.
Where to extract the backup with the
Warning: All files in that directory can be removed.
- The data path to use with --extract, the default is to use the fatest data path.
- Application property to send to the application with --extract.
- Leave dumps in the compressed/uncompressed and encrypted/unencrypted state in which they were found on tape. It is a synonym for --no-decompression --no-decryption
- 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.
John Stange <building [at] nap.edu>
- National Academies Press
Ian Turner <ian [at] zmanda.com>
- Zmanda, Inc. (http://www.zmanda.com)