NAME¶

amdump - back up all disks in an Amanda configuration

SYNOPSIS¶

amdump config [host [disk...]...] [-o configoption]...

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. 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.

OPTIONS¶

host [disk]*

-o configoption

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

amdump: amdump or amflush is already running, or you must run amcleanup

EXIT CODE¶

The exit code of amdump is the ORed value of:

 0  = success


 1  = error


 2  = a dle give strange message


 4  = a dle failed


 8  = Don´t know the status of a dle (RESULT_MISSING in the report)


 16 = tape error or no more tape

SEE ALSO¶

amanda(8), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(8), : http://wiki.zmanda.com

AUTHORS¶

James da Silva <jds@amanda.org>

Stefan G. Weichinger <sgw@amanda.org>