1AMDUMP(8)                                                            AMDUMP(8)
2
3
4

NAME

6       amdump - back up all disks in an Amanda configuration
7

SYNOPSIS

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

DESCRIPTION

12       Amdump switches to the appropriate Amanda configuration directory, e.g.
13       /usr/local/etc/amanda/config, then attempts to back up every disk
14       specified by the amanda.conf file.  Amdump is normally run by cron.
15
16       You can specify many host/disk expressions, only disks that match an
17       expression will be dumped. All disks are dumped if no expressions are
18       given.
19
20       If the file /usr/local/etc/amanda/config/hold exists, amdump will wait
21       until it is removed before starting the backups. This allows scheduled
22       backups to be delayed when circumstances warrant, for example, if the
23       tape device is being used for some other purpose. While waiting, amdump
24       checks for the hold file every minute.
25
26       See the amanda(8) man page for more details about Amanda.
27

OPTIONS

29       host [disk]*
30           Specify the host and disk on which the command will work.
31
32       -o configoption
33           See the "CONFIGURATION OVERWRITE" section in amanda(8).
34

EXAMPLE

36       Here is a typical crontab entry. It runs amdump every weeknight at 1
37       a.m. as user bin:
38
39           0 1 * * 1-5 bin /usr/local/sbin/amdump daily
40
41       Please see the crontab(5) or crontab(1) manual page for the correct
42       crontab format for your system.
43

MESSAGES

45       amdump: waiting for hold file to be removed
46           The "hold" file exists and amdump is waiting for it to be removed
47           before starting backups.
48
49       amdump: amdump or amflush is already running, or you must run amcleanup
50           Amdump detected another amdump or amflush running, or the remains
51           of a previous incomplete amdump or amflush run. This run is
52           terminated. If the problem is caused by the remains of a previous
53           run, you must execute amcleanup(8) and then rerun amdump.
54

AUTHOR

56       James da Silva, <jds@amanda.org> : Original text
57
58       Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the
59       Amanda-documentation: XML-conversion
60

SEE ALSO

62       amanda(8), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(8)
63
64
65
66                                  02/07/2007                         AMDUMP(8)
Impressum