3 Prev Chapter 35. The AMANDA Manual Pages. Next
5 -------------------------------------------------------------------------------
9 amdump
\14 back up all disks in an AMANDA configuration
13 amdump config [ host [disk...]...]
17 Amdump switches to the appropriate AMANDA configuration directory, e.g. /usr/
18 local/etc/amanda/config, then attempts to back up every disk specified by the
19 amanda.conf file. Amdump is normally run by cron.
20 You can specify many host/disk expressions, only disks that match an expression
21 will be dumped. All disks are dumped if no expressions are given.
22 If the file /usr/local/etc/amanda/config/hold exists, amdump will wait until it
23 is removed before starting the backups. This allows scheduled backups to be
24 delayed when circumstances warrant, for example, if the tape device is being
25 used for some other purpose. While waiting, amdump checks for the hold file
27 See the amanda(8) man page for more details about AMANDA.
31 Here is a typical crontab entry. It runs amdump every weeknight at 1 a.m. as
34 0 1 * * 1-5 bin /usr/local/sbin/amdump daily
36 Please see the crontab(5) or crontab(1) manual page for the correct crontab
37 format for your system.
43 amdump: waiting for hold file to be removed
44 The "hold" file exists and amdump is waiting for it to be removed before
47 amdump: amdump or amflush is already running, or you must run amcleanup
48 Amdump detected another amdump or amflush running, or the remains of a
49 previous incomplete amdump or amflush run. This run is terminated. If the
50 problem is caused by the remains of a previous run, you must execute
51 amcleanup(8) and then rerun amdump.
56 James da Silva, <jds@amanda.org> : Original text
57 Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the AMANDA-documentation:
62 amanda(8), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(8)
63 -------------------------------------------------------------------------------