Commands that take a hostname [ disks ] parameter pair operate on all disks in the disklist(5) for that hostname if no disks are
specified. Where hostname is also marked as being optional, the command operates on all hosts and disks in the disklist(5). Both hostname
and disks are special expressions; see the HOST & DISK EXPRESSION section of amanda(8) for a description.
Commands that take one or more dumpspec parameters operate on the set of dumps specified by all of the expressions. See the DUMP SPECIFICATIONS
section of amanda(8) for a description.
Show the current version and some compile time and runtime parameters. The config parameter must be present but is ignored.force-bump [ Force the disks on hostname to bump to a new incremental level during the next Amanda run.force-no-bump [ Force the disks on hostname to not bump to a new incremental level during the next Amanda run.unforce-bump [ Undo a previous force-bump or force-no-bump command.force [ Force the disks on hostname to do a full (level 0) backup during the next Amanda run.unforce [ Undo a previous force command.reuse The tapes listed will be available for reuse at their point in the tape cycle.no-reuse The tapes listed will not be reused when their turn comes up again in the tape cycle. Note that if this causes the number of reusable tapes to drop below
the amanda.conf tapecycle value, Amanda will request new tapes until the count is satisfied again.
Tape marked no-reuse are available for recovery, marking them no-reuse is a security to be sure amanda will not overwrite them.
due [ Show when the next full dump is due.find [ --sort Display all backups currently on tape or in the holding disk. The tape label or holding disk filename, file number, and status are displayed.
The --sort option changes the sort order using the following flags:
h: host name
k: disk name
d: dump timestamp
l: backup level
p: dump part
b: tape label
f: filenum on tape
w: write timestampAn uppercase letter reverses the sort order for that key. The default sort order is hkdlpbfw
.holding delete Delete holding files matching the given specification. At least a hostname must be provided.holding list [-l] [-d] [ List holding files matching the given specification, or all holding files if no specification is provided. With -l, additional information (size, level,
and whether the dump is outdated) is provided. With -d, only outdated dumps are shown.
An outdated holding file is one which is not required for a restore of the most recent dump. Note that outdated dumps may still be required for
restores at earlier dates. For example, assume that a DLE had a level 0 on Monday, level 1s Tuesday through Thursday, and a level 2 on Friday. Then the files
required for a restore of Fridays (the most recent) dump are those from Monday (level 0), Thursday (level 1), and Friday (level 2). Tuesday and Wednesdays
files are outdated.
delete [ Delete the specified disks on hostname from the Amanda database.Note
If you do not also remove the disk from the disklist
(5) file, Amanda will treat it as a new disk during the next run.tape
Display the tape
(s) Amanda expects to write to during the next run. See also amcheck
Display the current bump threshold parameters, calculated for all backup levels.balance [ --days Display the distribution of full backups throughout the dump schedule.export [ Convert records from the Amanda database to a text format that may be transmitted to another Amanda machine and import
ed records read from standard input to a form Amanda uses and insert them into the database on this machine.disklist [ Display the disklist
(5) information for each of the disks on hostname (or all hosts). Mostly used for debugging.info [ Display the database record for each of the disks on hostname (or all hosts). Mostly used for debugging.-o See the CONFIGURATION OVERRIDE
section in amanda
Request three specific file systems on machine-a get a full level 0 backup during the next Amanda run.$ force request for /home on disklist(5) file, disklist(5) yourself.
The balance column shows how far off that nights backups are from the average size (shown at the bottom of the balance column). Amanda tries
to keep the backups within +/- 5%, but since the amount of data on each filesystem is always changing, and Amanda will never delay backups just to
rebalance the schedule, it is common for the schedule to fluctuate by larger percentages. In particular, in the case of a tape or backup failure, a bump will
occur the following night, which will not be smoothed out until the next pass through the schedule.
The last line also shows an estimate of how many Amanda runs will be made between full backups for a file system. In the example, a file system will
probably have a full backup done every eight times Amanda is run (e.g. every eight days).$