12 amdump \- back up all disks in an Amanda configuration
24 switches to the appropriate Amanda configuration directory,
25 e.g. @CONFIG_DIR@/\fIconfig\fR,
26 then attempts to back up every disk specified by the
33 You can specify many host/disk expression, only disks that
34 match an expression will be dumped. All disk are dumped if no
37 If file @CONFIG_DIR@/\fIconfig\fR/hold exists,
39 will wait until it is removed before starting the backups.
40 This allows scheduled backups to be delayed when
41 circumstances warrant, for example, if the tape device is being
42 used for some other purpose.
45 checks for the hold file every minute.
49 man page for more details about Amanda.
51 Here is a typical crontab entry.
54 every weeknight at 1 a.m. as user
59 .ie '@sbindir@'${exec_prefix}/sbin' \{\
60 .ie '@exec_prefix@'${prefix}' .ds pr @prefix@/sbin
61 .el .ds pr @exec_prefix@/sbin\}
63 0 1 * * 1-5 bin \*(pr/amdump @DEFAULT_CONFIG@
71 manual page for the correct crontab format for your system.
74 amdump: waiting for hold file to be removed
75 The "hold" file exists and amdump is waiting for it to be removed
76 before starting backups.
78 amdump: amdump or amflush is already running, or you must run amcleanup
79 Amdump detected another amdump or amflush running,
80 or the remains of a previous incomplete amdump or amflush run.
81 This run is terminated.
82 If the problem is caused by the remains of a previous run,
88 James da Silva <jds@cs.umd.edu>
90 University of Maryland, College Park