Amcheckdump: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
==NAME== | ==NAME== | ||
| Line 8: | Line 6: | ||
==SYNOPSIS== | ==SYNOPSIS== | ||
amcheckdump config [--timestamp|-t timestamp] | amcheckdump config [--timestamp|-t timestamp] [-o configoption] ... | ||
==DESCRIPTION== | ==DESCRIPTION== | ||
| Line 17: | Line 15: | ||
If a changer is available, it is used to load the required tapes. Otherwise, the application interactively requests the tapes. | If a changer is available, it is used to load the required tapes. Otherwise, the application interactively requests the tapes. | ||
See the "[[amanda#CONFIGURATION_OVERRIDE|CONFIGURATION OVERRIDE]]" section in [[amanda]](8) for information on the -o option. | |||
==EXAMPLE== | ==EXAMPLE== | ||
Revision as of 19:40, 7 February 2008
NAME
amcheckdump - check the results of an Amanda dump
SYNOPSIS
amcheckdump config [--timestamp|-t timestamp] [-o configoption] ...
DESCRIPTION
Amcheckdump verifies Amanda dump images by reading them from storage volume(s) and verifying that the images can be parsed by the appropriate application (if available). For example, a GNUTAR image is passed to GNU Tar for parsing, and any errors (e.g., corrupt or missing data) are noted.
The application runs on the most recent dump or, if --timestamp is specified, on the most recent dump with that timestamp. Note that the verification is local to the Amanda server; if the dump application is not available, or is configured differently on the server than on the client, then the verification will most likely fail.
If a changer is available, it is used to load the required tapes. Otherwise, the application interactively requests the tapes.
See the "CONFIGURATION OVERRIDE" section in amanda(8) for information on the -o option.
EXAMPLE
Check the most recent dump
amcheckdump MYCONFIG
Check a specific dump from back in '78
amcheckdump MYCONFIG --timestamp 19780615
SEE ALSO
amanda(5)