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] [--no-dump] [--no-flush] [--no-vault]
10              [--exact-match] [-o configoption...] config [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       --no-taper
36           Disable writting to tape, including flush and vault.
37
38       --no-dump
39           Disable dump operations.
40
41       --no-flush
42           Disable flush, like setting autoflush to NO for all storages.
43
44           Dump done in this run will be flushed.
45
46       --no-vault
47           Disable all vault.
48
49       --exact-match
50           The host and disk are parsed as exact values.
51
52       -o configoption
53           See the "CONFIGURATION OVERRIDE" section in amanda(8).
54
55       host [disk]*
56           Specify the host and disk on which the command will work -- see the
57           description of DLE specifications in amanda-match(7).
58

EXAMPLE

60       Here is a typical crontab entry. It runs amdump every weeknight at 1
61       a.m. as user bin:
62       0 1 * * 1-5 bin /usr/local/sbin/amdump daily
63
64       Please see the crontab(5) or crontab(1) manual page for the correct
65       crontab format for your system.
66

MESSAGES

68       amdump: waiting for hold file to be removed
69           The "hold" file exists and amdump is waiting for it to be removed
70           before starting backups.
71
72       amdump: amdump or amflush is already running, or you must run amcleanup
73           Amdump detected another amdump or amflush running, or the remains
74           of a previous incomplete amdump or amflush run. This run is
75           terminated. If the problem is caused by the remains of a previous
76           run, you must execute amcleanup(8) and then rerun amdump.
77

EXIT CODE

79       The exit code of amdump is the ORed value of:
80        0  = success
81        1  = error
82        2  = a dle give strange message
83        4  = a dle failed
84        8  = Don't know the status of a dle (RESULT_MISSING in the report)
85        16 = tape error or no more tape
86

AUTHORS

94       James da Silva <jds@amanda.org>
95
96       Stefan G. Weichinger <sgw@amanda.org>
97
98
99
100Amanda 3.5.1                      12/01/2017                         AMDUMP(8)