amdump(8)

1AMDUMP(8)               System Administration Commands               AMDUMP(8)
2
3
4

NAME

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

SYNOPSIS

9       amdump [--no-taper] [--exact-match] [-o configoption...] config
10              [host [disk...]...]
11

DESCRIPTION

13       Amdump is the main interface to the Amanda backup process. It loads the
14       specified configuration and attempts to back up every disk specified by
15       the disklist(5).  Amdump is normally run by cron.
16
17       The command optionally takes a set of DLE specifications (see amanda-
18       match(7)) to narrow the DLEs that will be dumped. All disks are dumped
19       if no expressions are given.
20
21       If a file named hold exists in the configuration directory, amdump will
22       wait until it is removed before starting the backups. This allows
23       scheduled backups to be delayed when circumstances warrant, for
24       example, if the tape device is being used for some other purpose. While
25       waiting, amdump checks for the hold file every minute.
26
27       In some cases it is desirable to dump all Amanda clients to holding
28       disk without writing anything to storage media. The --no-taper option
29       instructs Amanda to not start the taper, and thus enter degraded mode
30       immediately.
31
32       See the amanda(8) man page for more details about Amanda.
33

OPTIONS

35       host [disk]*
36           Specify the host and disk on which the command will work -- see the
37           description of DLE specifications in amanda-match(7).
38
39       --exact-match
40           The host and disk are parsed as exact values
41
42       -o configoption
43           See the "CONFIGURATION OVERRIDE" section in amanda(8).
44

EXAMPLE

46       Here is a typical crontab entry. It runs amdump every weeknight at 1
47       a.m. as user bin:
48       0 1 * * 1-5 bin /usr/local/sbin/amdump daily
49
50       Please see the crontab(5) or crontab(1) manual page for the correct
51       crontab format for your system.
52

MESSAGES

54       amdump: waiting for hold file to be removed
55           The "hold" file exists and amdump is waiting for it to be removed
56           before starting backups.
57
58       amdump: amdump or amflush is already running, or you must run amcleanup
59           Amdump detected another amdump or amflush running, or the remains
60           of a previous incomplete amdump or amflush run. This run is
61           terminated. If the problem is caused by the remains of a previous
62           run, you must execute amcleanup(8) and then rerun amdump.
63

EXIT CODE

65       The exit code of amdump is the ORed value of:
66        0  = success
67        1  = error
68        2  = a dle give strange message
69        4  = a dle failed
70        8  = Don't know the status of a dle (RESULT_MISSING in the report)
71        16 = tape error or no more tape
72

AUTHORS

80       James da Silva <jds@amanda.org>
81
82       Stefan G. Weichinger <sgw@amanda.org>
83
84
85
86Amanda 3.3.3                      01/10/2013                         AMDUMP(8)