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.
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), amanda-match(7), amadmin(8), amrestore(8)
The Amanda Wiki: : http://wiki.zmanda.com/
John Stange <firstname.lastname@example.org>
Ian Turner <email@example.com>