go to
> amanda(8)
> amanda-match(7)
> amadmin(8)
> amrestore(8)
Homepage > Man Pages > Category > Maintenance Commands
Homepage > Man Pages > Name > A

amfetchdump

man page of amfetchdump

amfetchdump: extract backup images from multiple Amanda tapes.

NAME

amfetchdump - extract backup images from multiple Amanda tapes.

SYNOPSIS

amfetchdump [-phcClawns] [-d device] [-O directory] [-b blocksize] [--header-fd fd] [--header-file filename] [-o configoption...] config hostname [disk [ date [ level [ hostname [...] ] ] ]]

DESCRIPTION

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 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. hostname.diskname.datestamp.dumplevel

OPTIONS

-p 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). -h Output the amanda header as a 32K block to same output as the image. --header-fd fd Output the amanda header to the numbered file descriptor. --header-file filename Output the amanda header to the filename. -d device_or_changer Restore from this device or changer instead of the default, prompting for each volume. -O directory Output restored files to this directory, instead of to the current working directory. -c Compress output, fastest method available. -C Compress output, smallest file size method available. -l Leave dumps in the compressed/uncompressed state in which they were found on tape. By default, amfetchdump will automatically uncompress when restoring. -a Assume that all tapes are already available, via tape changer or otherwise, instead of prompting the operator to ensure that all tapes are loaded. -n Do not reassemble split dump files at all, just restore each piece as an individual file. -o configoption See the "CONFIGURATION OVERRIDE" section in amanda(8).
EXAMPLES
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 -
CAVEATS
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.

SEE ALSO

amanda(8), amanda-match(7), amadmin(8), amrestore(8) The Amanda Wiki: : //wiki.zmanda.com/

AUTHORS

John Stange <building@nap.edu> National Academies Press Ian Turner <ian@zmanda.com> Zmanda, Inc. AMFETCHDUMP(8)
 
 
 

Copyright © 2011–2018 by topics-of-interest.com . All rights reserved. Hosted by all-inkl.
Contact · Imprint · Privacy

Page generated in 26.80ms.

doomsdaydude.de | www.daelim-forum.com | daelim-forum.spreadshirt.de