A descriptive name for the configuration. This string is used for mail reports. Each Amanda configuration should have a different value.
A comma separated list of recipients for mail reports.
The number of days in the backup cycle. Each disk will get a full backup no less often than this many days.
Suffixes: day, days, week, weeks
The number of amdump runs in dumpcycle days.
A value of 0 means the same value as dumpcycle. A value of -1 means guess the number of runs from the tapelist file, which is the number of tape used in the last dumpcycle days / runtapes.
The number of tapes in your active tape cycle.
This must be at least one larger than the number of Amanda runs done during a dump cycle (see the dumpcycle parameter) times the number of tapes used per run (see the runtapes parameter).
For instance, if you have dumpcycle set to 14 days, do one Amanda run per day and have runtapes set to one, tapecycle must be at least 15 (14 days * one run/day * one tape/run + one tape).
In practice you should have five or more extra tapes to allow for schedule adjustments or disaster recovery.
The login name Amanda uses to run the backups.
The backup client hosts must allow access from the tape server host as this user via .rhosts or .amandahosts, depending on how the Amanda software was built.
The maximum number of tapes used in a single run.
If you do not have a tape changer, this option is not used and should be left blank.
Suffixes: tape, tapes
Amount of time per disk on a given client that planner will wait to get the dump size estimates.
For instance, with the default of 300 seconds and four disks on client A, planner will wait up to 20 minutes for that machine. A negative value will be interpreted as a total amount of time, instead of a per-disk value.
The maximum network bandwidth allocated to Amanda, in Kbytes per second.
See also the interface section.
The maximum number of backups that Amanda will attempt to run in parallel.
Amanda will stay within the constraints of network bandwidth and holding disk space available, so it doesn't hurt to set this number a bit high. Some contention can occur with larger numbers of backups, but this effect is relatively small on most systems.
The maximum number of backups from a single host that Amanda will attempt to run in parallel. See also the dumptype section and in parallel option.
The minimum savings required to trigger an automatic bump from one incremental level to the next.
If Amanda determines that the next higher backup level will be this much smaller than the current level, it will do the next level. See also the Bump multiplier setting.
The bump multiplier.
Amanda multiplies bumpsize by this factor for each level. This prevents active filesystems from bumping too much by making it harder to bump to the next level. For example, with the default bumpsize and bumpmult set to 2.0, the bump threshold will be 10 Mbytes for level one, 20 Mbytes for level two, 40 Mbytes for level three, and so on.
To insure redundancy in the dumps, Amanda will keep filesystems at the same incremental level for at least bumpdays days, even if the bump threshold criteria are met.
The amount of holding-disk space that should not be used for full backups if no tape is available.
By default, when there is no tape to write to, degraded mode (incremental) backups will be performed to the holding disk. If you wish to also allow full backups in this case, you may reduce the amount of holding disk space reserved for incrementals.