amdump - back up all disks in an Amanda configuration
amdump config [ host [ disk ]* ]*
Amdump switches to the appropriate Amanda configuration directory, e.g. /etc/amanda/con-
fig, then attempts to back up every disk specified by the amanda.conf file. Amdump is
normally run by cron.
You can specify many host/disk expression, only disks that match an expression will be
dumped. All disk are dumped if no expression are given.
If file /etc/amanda/config/hold exists, amdump will wait until it is removed before start-
ing 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.
Here is a typical crontab entry. It runs amdump every weeknight at 1 a.m. as user bin:
0 1 * * 1-5 bin /usr/sbin/amdump DailySet1
Please see the crontab(5) or crontab(1) manual page for the correct crontab format for
amdump: waiting for hold file to be removed
The "hold" file exists and amdump is waiting for it to be removed before starting
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
James da Silva <email@example.com>
University of Maryland, College Park
amanda(8), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(8)