amdump - back up all disks in an Amanda configuration
SYNOPSIS
amdump config
DESCRIPTION
Amdump switches to the appropriate Amanda configuration
directory, e.g. /etc/amanda/config, then attempts to back
up every disk specified by the amanda.conf file. Amdump
is normally run by cron.
If file /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/sbin/amdump DailySet1
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 prob
lem is caused by the remains of a previous run, you
must execute amcleanup(8) and then rerun amdump.
AUTHOR
James da Silva <jds@cs.umd.edu>
University of Maryland, College Park
SEE ALSO
amanda(8), amcheck(8), amcleanup(8), amrestore(8),
amflush(8), cron(8)
Man(1) output converted with
man2html