X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=man%2Fxml-source%2Famfetchdump.8.xml;h=5b443a0f13e9dac6bf176f6bb2a679f0cef85e92;hb=691567b16c13087b31ee4c2b6d038e57872fae82;hp=4f4d4a3878679c7f74491d2dc1239d7b37cc1520;hpb=34197d9f46a5f4e944378cbb65fca32ee0eec7b9;p=debian%2Famanda diff --git a/man/xml-source/amfetchdump.8.xml b/man/xml-source/amfetchdump.8.xml index 4f4d4a3..5b443a0 100644 --- a/man/xml-source/amfetchdump.8.xml +++ b/man/xml-source/amfetchdump.8.xml @@ -3,7 +3,7 @@ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ - + %global_entities; ]> @@ -12,20 +12,59 @@ amfetchdump 8 +&rmi.source; +&rmi.version; +&rmi.manual.8; amfetchdump -extract backup images from multiple &A; tapes. +extract backup images from multiple Amanda tapes. + +&author.jstange; +&author.ian; + amfetchdump - -pcClawns - -d device + + -c + -C + -l + + + -p + -n + + -a -O directory - -i logfile - -b blocksize + -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 + &configoverride.synopsis; config hostname @@ -41,7 +80,6 @@ - -o configoption @@ -50,31 +88,30 @@ 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. +tape autochanger operations. The dump are by default decompressed and decrypted. + -It will automatically use the logs created by -amdump8 +It will automatically use the Amanda catalog to locate available dumps on tape, in the same way that the find feature of -amadmin8 -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. + +lists available dumps. The hostname, diskname, datestamp, and -level dump pattern-matching works as in -amrestore8, -with the added requirement that at minimum a hostname must be specified when not in inventory mode. +level dump specifications are further described in +. +Note that at minimum a hostname must be specified. -Unless - +Unless is used, backup images are extracted to files in the current directory named: +If a changer error occurs, or the option is given, +then amfetchdump prompts for each required volume. + hostname.diskname.datestamp.dumplevel @@ -91,8 +128,22 @@ will restore only the first matching dumpfile (where facility). - device - Restore from this tape device instead of the default. + +Output the amanda header as a 32K block to same output as the image. + + + fd +Output the amanda header to the numbered file + descriptor. + + + filename +Output the amanda header to the filename. + + + device_or_changer + Restore from this device or changer instead of the default, +prompting for each volume. @@ -111,66 +162,106 @@ facility). available. - -Leave dumps in the compressed/uncompressed state in which they -were found on tape. By default, amfetchdump will automatically uncompress when -restoring. + + Always do the decompression, this is the default. - -Assume that all tapes are already available, via tape changer or -otherwise, instead of prompting the operator to ensure that all tapes -are loaded. + + Never do the decompression. + + + + Do the decompression only if the compression was done on +the server. - filename -Generate an inventory of all dumps "seen" on the -tapes we search, for later use as a log. + + Do the decompression only if the compression was done on +the client. - -Wait to put split dumps together until all chunks have been -restored. Normally, amfetchdump will -attempt to read pieces of a split file from tape in order, so that it -can assemble them simply by appending each file to the first. This -option disables the appending behavior, and instead restores each -piece as an individual file and reassembles them only after all have -been restored. + + 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. + -This requires at least double the size of your dump in free -disk space, in order to build the final assembled dumpfile. - + + + +The host and disk are parsed as exact values + + -This behavior is implicitly invoked in circumstances where knowing the -location of all dumps on tape in advance is not possible, such as when -you are restoring without log files. + + + +Extract the backup on the server in the +directory directory. + + - -Do not reassemble split dump files at all, just restore each -piece as an individual file. + directory + +Where to extract the backup with the option. +Warning: All files in that directory can be removed. + + + + + amanda|directtcp + +The data path to use with , the default is + to use the fatest data path. + + + + + NAME=VALUE + +Application property to send to the application with + + + + + + +Leave dumps in the compressed/uncompressed and +encrypted/unencrypted state in which they were found on tape. +It is a synonym for + - -Do not fast-forward straight to needed files on tape. This will -slow down most restores substantially. Only use this option if your -tape drive does not properly support the fast-forward -operation. + +Assume that all tapes are already available, via tape changer or +otherwise, instead of prompting the operator to ensure that all tapes +are loaded. + - - blocksize -Force a particular block size when reading from tapes. This - value will usually be autodetected, and should not normally need - to be set. + +Do not reassemble split dump files at all, just restore each +piece as an individual file. - -o configoption + configoption -See the "CONFIGURATION OVERWRITE" - section in amanda8. +See the "CONFIGURATION OVERRIDE" + section in . @@ -183,39 +274,17 @@ operation. 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 &gnutar; as well, to automatically extract the dump. - - + $ amfetchdump -p SetA vanya /home 20051020 | gtar -xvpf - - - -In a situation where all of our dump logs have been wiped out, -we could also use amfetchdump to inventory our tapes and recreate an -imitation of those logs, which we'll send to stdout for casual perusal. - - -$ amfetchdump -i - SetA - - + -Note that you can specify a restore while in inventory mode, and -amfetchdump will continue searching for more dumps -from this host even after successfully restoring a dump, inventorying -all the while. If your backup searcher has been trashed, this is a -handy way to recover what you have. - - -$ amfetchdump -i /var/amanda/log SetA backupserver - - CAVEATS @@ -225,23 +294,17 @@ 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 -amrestore8 + or -dd8 + instead. -AUTHOR -John Stange, &email.jstange;, National Academies Press -Ian Turner, &email.itt;: XML-conversion - + +, +, +, + -SEE ALSO -amanda8, -amadmin8, -amrestore8, -tar1 -restore8 -