Amdump: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==Name== | ==Name== | ||
amdump — back up all disks in an | amdump — back up all disks in an Amanda configuration | ||
==Synopsis== | ==Synopsis== | ||
| Line 9: | Line 9: | ||
==DESCRIPTION== | ==DESCRIPTION== | ||
Amdump switches to the appropriate | Amdump switches to the appropriate Amanda configuration directory, e.g. /usr/local/etc/amanda/config, then attempts to back up every disk specified by the amanda.conf file and disklist file. Amdump is normally run by cron. | ||
You can specify many host/disk expressions, only disks that match an expression will be dumped. All disks are dumped if no expressions are given. | You can specify many host/disk expressions, only disks that match an expression will be dumped. All disks are dumped if no expressions are given. | ||
| Line 15: | Line 15: | ||
If the file /usr/local/etc/amanda/config/hold exists, amdump will wait until it is removed before starting the backups. This allows scheduled backups to be delayed when circumstances warrant, for example, if the tape device is being used for some other purpose. While waiting, amdump checks for the hold file every minute. | If the file /usr/local/etc/amanda/config/hold exists, amdump will wait until it is removed before starting the backups. This allows scheduled backups to be delayed when circumstances warrant, for example, if the tape device is being used for some other purpose. While waiting, amdump checks for the hold file every minute. | ||
See the amanda(8) man page for more details about AMANDA. | See the [[amanda]](8) man page for more details about AMANDA. | ||
==EXAMPLE== | ==EXAMPLE== | ||
| Line 21: | Line 21: | ||
Here is a typical crontab entry. It runs amdump every weeknight at 1 a.m. as user bin: | Here is a typical crontab entry. It runs amdump every weeknight at 1 a.m. as user bin: | ||
0 1 * * 1-5 bin /usr/local/sbin/amdump daily | 0 1 * * 1-5 bin /usr/local/sbin/amdump daily | ||
Please see the crontab(5) or crontab(1) manual page for the correct crontab format for your system. | Please see the crontab(5) or crontab(1) manual page for the correct crontab format for your system. | ||
| Line 27: | Line 27: | ||
==MESSAGES== | ==MESSAGES== | ||
amdump: waiting for hold file to be removed | ; <nowiki> amdump: waiting for hold file to be removed </nowiki> : The "hold" file exists and amdump is waiting for it to be removed before starting backups. | ||
; <nowiki> amdump: amdump or amflush is already running, or you must run amcleanup </nowiki> : Amdump detected another amdump or amflush running, or the remains of a previous incomplete amdump or amflush run. This run is terminated. If the problem is caused by the remains of a previous run, you must execute [[amcleanup]](8) and then rerun amdump. | |||
amdump: amdump or amflush is already running, or you must run amcleanup | |||
Amdump detected another amdump or amflush running, or the remains of a previous incomplete amdump or amflush run. This run is terminated. If the problem is caused by the remains of a previous run, you must execute amcleanup(8) and then rerun amdump. | |||
==AUTHOR== | ==AUTHOR== | ||
| Line 43: | Line 39: | ||
==SEE ALSO== | ==SEE ALSO== | ||
amanda(8), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(8) | [[amanda]](8), [[amcheck]](8), [[amcleanup]](8), [[amrestore]](8), [[amflush]](8), cron(8) | ||
Revision as of 23:39, 28 November 2005
Name
amdump — back up all disks in an Amanda configuration
Synopsis
amdump config [ host [disk...]...]
DESCRIPTION
Amdump switches to the appropriate Amanda configuration directory, e.g. /usr/local/etc/amanda/config, then attempts to back up every disk specified by the amanda.conf file and disklist file. Amdump is normally run by cron.
You can specify many host/disk expressions, only disks that match an expression will be dumped. All disks are dumped if no expressions are given.
If the file /usr/local/etc/amanda/config/hold exists, amdump will wait until it is removed before starting the backups. This allows scheduled backups to be delayed when circumstances warrant, for example, if the tape device is being used for some other purpose. While waiting, amdump checks for the hold file every minute.
See the amanda(8) man page for more details about AMANDA.
EXAMPLE
Here is a typical crontab entry. It runs amdump every weeknight at 1 a.m. as user bin:
0 1 * * 1-5 bin /usr/local/sbin/amdump daily
Please see the crontab(5) or crontab(1) manual page for the correct crontab format for your system.
MESSAGES
- amdump: waiting for hold file to be removed
- The "hold" file exists and amdump is waiting for it to be removed before starting backups.
- amdump: amdump or amflush is already running, or you must run amcleanup
- Amdump detected another amdump or amflush running, or the remains of a previous incomplete amdump or amflush run. This run is terminated. If the problem is caused by the remains of a previous run, you must execute amcleanup(8) and then rerun amdump.
AUTHOR
James da Silva, <[email protected]> : Original text
Stefan G. Weichinger, <[email protected]>, maintainer of the AMANDA-documentation: XML-conversion
SEE ALSO
amanda(8), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(8)