AMDUMP(8)
π AMDUMP β the one that backs up all your disks π
okay bestie, gather round, because amdump is the main character of the Amanda backup cinematic universe β¨ it lives in section 8 of the system administration commands manual, and it is genuinely the moment everything else has been waiting for π
πΈ NAME πΈ
amdump β back up all disks in an Amanda configuration π¦
β¨ SYNOPSIS β¨
amdump [--no-taper] [--no-dump] [--no-flush] [--no-vault]
[--exact-match] [-o configoption...] config [host [disk...]...]
π DESCRIPTION π
So Amdump is, like, the main interface to the Amanda backup process. no cap. It loads the config you point it at and then attempts to back up every single disk that the disklist(5) says to back up. And yeah, Amdump is normally run by cron, because it's that friend who just shows up at 1am and handles business π
The command optionally takes a set of DLE specifications (peep amanda-match(7) for the whole lore) to narrow down which DLEs actually get dumped. If you give it no expressions at all? Every disk gets dumped. all of them. periodt π
Now here's a cute detail β if a file named hold exists in the configuration directory, amdump will wait until it gets removed before starting the backups β This is so scheduled backups can be delayed when circumstances warrant it, for example if the tape device is being used for some other purpose. While it's waiting, amdump checks for the hold file every minute (very patient, very demure π§).
In some cases it's desirable to dump all Amanda clients to holding disk without writing anything to storage media. The --no-taper option tells Amanda to not start the taper, which means it enters degraded mode immediately. it's giving intentional chaos π
See the amanda(8) man page for way more details about Amanda, bestie.
π OPTIONS π
--no-taperβ Disable writting to tape, including flush and vault. (yes girl, we're keeping the typo, it's iconic, do not come for me π)--no-dumpβ Disable dump operations. that's it. no dumping today π--no-flushβ Disable flush, like settingautoflushtoNOfor all storages. But heads up bestie: Dump done in this run will be flushed. π₯--no-vaultβ Disable all vault.--exact-matchβ The host and disk are parsed as exact values.-oconfigoption β See the "CONFIGURATION OVERRIDE" section inamanda(8).- host [disk]* β Specify the host and disk on which the command will work β see the description of DLE specifications in
amanda-match(7).
π EXAMPLE π
Here is a typical crontab entry. It runs amdump every weeknight at 1 a.m. as user bin:
0 1 * * 1-5 bin /usr/local/sbin/amdump daily
Please see the crontab(5) or crontab(1) manual page for the correct crontab format for your system. (every system is a little different, she contains multitudes π)
π MESSAGES π
amdump: waiting for hold file to be removedThe"hold"file exists andamdumpis waiting for it to be removed before starting backups. she's just standing there. politely. β³amdump: amdump or amflush is already running, or you must run amcleanupAmdumpdetected anotheramdumporamflushrunning, or the remains of a previous incompleteamdumporamflushrun. This run is terminated. π If the problem is caused by the remains of a previous run, you must executeamcleanup(8)and then rerunamdump.
π EXIT CODE π
The exit code of amdump is the ORed value of:
0 = success
1 = error
2 = a dle give strange message
4 = a dle failed
8 = Don't know the status of a dle (RESULT_MISSING in the report)
16 = tape error or no more tape
π SEE ALSO π
amanda(8), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(8), amanda-match(7)
The Amanda Wiki: : http://wiki.zmanda.com/ β¨
π«Ά AUTHORS π«Ά
- James da Silva
<jds@amanda.org> - Stefan G. Weichinger
<sgw@amanda.org>
and that's the whole vibe check, bestie π this page is from Amanda 3.5.4, dated 08/26/2026 β go forth and back up your disks, you absolute icon ππ
π¦ where this page comes from
- ubuntu stonking: amanda-common 1:3.5.4-2.1ubuntu1 Β· Custom
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms