-Integer arguments may have one of the following (case insensitive) suffixes, some of which have a multiplier effect:
-
-.TP
-\fBb byte bytes\fR
-Some number of bytes\&.
-
-.TP
-\fBbps\fR
-Some number of bytes per second\&.
-
-.TP
-\fBk kb kbyte kbytes kilobyte kilobytes\fR
-Some number of kilobytes (bytes*1024)\&.
-
-.TP
-\fBkps kbps\fR
-Some number of kilobytes per second (bytes*1024)\&.
-
-.TP
-\fBm mb meg mbyte mbytes megabyte megabytes\fR
-Some number of megabytes (bytes*1024*1024)\&.
-
-.TP
-\fBmps mbps\fR
-Some number of megabytes per second (bytes*1024*1024)\&.
-
-.TP
-\fBg gb gbyte gbytes gigabyte gigabytes\fR
-Some number of gigabytes (bytes*1024*1024*1024)\&.
-
-.TP
-\fBtape tapes\fR
-Some number of tapes\&.
-
-.TP
-\fBday days\fR
-Some number of days\&.
-
-.TP
-\fBweek weeks\fR
-Some number of weeks (days*7)\&.
-
- .RS .Sh "Note" The value \fBinf\fR may be used in most places where an integer is expected to mean an infinite amount\&. Boolean arguments may have any of the values \fBy\fR, \fByes\fR, \fBt\fR, \fBtrue\fR or \fBon\fR to indicate a true state, or \fBn\fR, \fBno\fR, \fBf\fR, \fBfalse\fR or \fBoff\fR to indicate a false state\&. If no argument is given, \fBtrue\fR is assumed\&. .RE
-
-.TP
-\fBorg\fR \fB string\fR
-Default: \fBdaily\fR\&. A descriptive name for the configuration\&. This string appears in the Subject line of mail reports\&. Each \fBAMANDA\fR configuration should have a different string to keep mail reports distinct\&.
-
-.TP
-\fBmailto\fR \fB string\fR
-Default: \fBoperators\fR\&. A space separated list of recipients for mail reports\&.
-
-.TP
-\fBdumpcycle\fR \fB int\fR
-Default: \fB10 days\fR\&. The number of days in the backup cycle\&. Each disk will get a full backup at least this often\&. Setting this to zero tries to do a full backup each run\&.
-
- .RS .Sh "Note" This parameter may also be set in a specific \fBdumptype\fR (see below)\&. This value sets the default for all \fBdumptype\fRs so must appear in \fBamanda\&.conf\fR before any \fBdumptype\fRs are defined\&. .RE
-
-.TP
-\fBrunspercycle\fR \fB int\fR
-Default: \fBsame as dumpcycle\fR\&. The number of amdump runs in \fBdumpcycle\fR days\&. A value of 0 means the same value as \fBdumpcycle\fR\&. A value of \-1 means guess the number of runs from the \fBtapelist\fR file, which is the number of tapes used in the last \fBdumpcycle\fR days / \fBruntapes\fR\&.
-
-.TP
-\fBtapecycle\fR \fB int\fR
-Default: \fB15 tapes\fR\&. Typically tapes are used by \fBAMANDA\fR in an ordered rotation\&. The \fBtapecycle\fR parameter defines the size of that rotation\&. The number of tapes in rotation must be larger than the number of tapes required for a complete dump cycle (see the \fBdumpcycle\fR parameter)\&.
-
-This is calculated by multiplying the number of \fBamdump\fR runs per dump cycle (\fBrunspercycle\fR parameter) times the number of tapes used per run (\fBruntapes\fR parameter)\&. Typically two to four times this calculated number of tapes are in rotation\&. While \fBAMANDA\fR is always willing to use a new tape in its rotation, it refuses to reuse a tape until at least '\fBtapecycle\fR \-1' number of other tapes have been used\&.
-
-It is considered good administrative practice to set the \fBtapecycle\fR parameter slightly lower than the actual number of tapes in rotation\&. This allows the administrator to more easily cope with damaged or misplaced tapes or schedule adjustments that call for slight adjustments in the rotation order\&.
-
-.TP
-\fBdumpuser\fR \fB string\fR
-Default: \fBamanda\fR\&. The login name \fBAMANDA\fR 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 \fBAMANDA\fR software was built\&.
-
-.TP
-\fBprinter\fR string
-Printer to use when doing tape labels\&. See the \fBlbl\-templ\fR \fBtapetype\fR option\&.
-
-.TP
-\fBtapedev\fR string
-Default: \fI/dev/nst0\fR\&. The path name of the non\-rewinding tape device\&. Non\-rewinding tape device names often have an 'n' in the name, e\&.g\&. \fI/dev/rmt/0mn\fR, however this is operating system specific and you should consult that documentation for detailed naming information\&.
-
-If a tape changer is configured (see the \fBtpchanger\fR option), this option might not be used\&.
-
-If the \fBnull\fR output driver is selected (see the OUTPUT DRIVERS section later for more information), programs such as \fBamdump\fR will run normally but all images will be thrown away\&. This should only be used for debugging and testing, and probably only with the \fBrecord\fR option set to \fBno\fR\&.
-
-.TP
-\fBrawtapedev\fR string
-Default: \fI/dev/null\fR\&. The path name of the raw tape device\&. This is only used if \fBAMANDA\fR is compiled for Linux machines with floppy tapes and is needed for QIC volume table operations\&.
-
-.TP
-\fBtpchanger\fR string
-Default: \fBnone\fR\&. The name of the tape changer\&. If a tape changer is not configured, this option is not used and should be commented out of the configuration file\&.
-
-If a tape changer is configured, choose one of the changer scripts (e\&.g\&. \fBchg\-scsi\fR) and enter that here\&.
-
-.TP
-\fBchangerdev\fR string
-Default: \fI/dev/null\fR\&. A tape changer configuration parameter\&. Usage depends on the particular changer defined with the \fBtpchanger\fR option\&.
-
-.TP
-\fBchangerfile\fR string
-Default: \fI/usr/adm/amanda/log/changer\-status\fR\&. A tape changer configuration parameter\&. Usage depends on the particular changer defined with the \fBtpchanger\fR option\&.
-
-.TP
-\fBruntapes\fR int
-Default: 1\&. The maximum number of tapes used in a single run\&. If a tape changer is not configured, this option is not used and should be commented out of the configuration file\&.
-
-If a tape changer is configured, this may be set larger than one to let \fBAMANDA\fR write to more than one tape\&.
-
-Note that this is an upper bound on the number of tapes, and \fBAMANDA\fR may use less\&.
-
-Also note that as of this release, \fBAMANDA\fR does not support true tape overflow\&. When it reaches the end of one tape, the backup image \fBAMANDA\fR was processing starts over again on the next tape\&.
-
-.TP
-\fBmaxdumpsize\fR int
-Default: \fBruntapes\fR*\fBtape_length\fR\&. Maximum number of bytes the planner will schedule for a run\&.
-
-.TP
-\fBtaperalgo\fR [first|firstfit|largest|largestfit|smallest|last]
-Default: \fBfirst\fR\&. The algorithm used to choose which dump image to send to the taper\&.
-
-.RS
-
-.TP
-\fBfirst\fR
-First in, first out\&.
-
-.TP
-\fBfirstfit\fR
-The first dump image that will fit on the current tape\&.
-
-.TP
-\fBlargest\fR
-The largest dump image\&.
-
-.TP
-\fBlargestfit\fR
-The largest dump image that will fit on the current tape\&.
-
-.TP
-\fBsmallest\fR
-The smallest dump image\&.
-
-.TP
-\fBlast\fR
-Last in, first out\&.
-
-.RE
-.IP
-
-.TP
-\fBlabelstr\fR \fB string\fR
-Default: \fB\&.*\fR\&. The tape label constraint regular expression\&. All tape labels generated (see \fBamlabel(8)\fR) and used by this configuration must match the regular expression\&. If multiple configurations are run from the same tape server host, it is helpful to set their labels to different strings (for example, ``\fBDAILY[0\-9][0\-9]*\fR'' vs\&. ``\fBARCHIVE[0\-9][0\-9]*\fR'') to avoid overwriting each other's tapes\&.
-
-.TP
-\fBtapetype\fR \fB string\fR
-Default: \fBEXABYTE\fR\&. The type of tape drive associated with \fBtapedev\fR or \fBtpchanger\fR\&. This refers to one of the defined \fBtapetype\fRs in the config file (see below), which specify various tape parameters, like the \fBlength\fR, \fBfilemark\fR size, and \fBspeed\fR of the tape media and device\&.
-
-.TP
-\fBctimeout\fR int
-Default: \fB30 seconds\fR\&. Maximum amount of time that \fBamcheck\fR will wait for each client host\&.
-
-.TP
-\fBdtimeout\fR int
-Default: \fB1800 seconds\fR\&. Amount of idle time per disk on a given client that a \fBdumper\fR running from within \fBamdump\fR will wait before it fails with a data timeout error\&.
-
-.TP
-\fBetimeout\fR int
-Default: \fB300 seconds\fR\&. Amount of time per disk on a given client that the \fBplanner\fR step of \fBamdump\fR will wait to get the dump size estimates\&. For instance, with the default of 300 seconds and four disks on client A, \fBplanner\fR will wait up to 20 minutes for that machine\&. A negative value will be interpreted as a total amount of time to wait per client instead of per disk\&.
-
-.TP
-\fBnetusage\fR int
-Default: \fB300 Kbps\fR\&. The maximum network bandwidth allocated to \fBAMANDA\fR, in Kbytes per second\&. See also the \fBinterface\fR section\&.
-
-.TP
-\fBinparallel\fR int
-Default: 10\&. The maximum number of backups that \fBAMANDA\fR will attempt to run in parallel\&. \fBAMANDA\fR 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\&.
-
-.TP
-\fBdisplayunit\fR "k|m|g|t"
-Default: "k"\&. The unit used to print many numbers, k=kilo, m=mega, g=giga, t=tera\&.
-
-.TP
-\fBdumporder\fR string
-Default: \fBtttTTTTTTT\fR\&. The priority order of each dumper:
-
-.RS
-.TP 3
-\(bu
-s: smallest size
-.TP
-\(bu
-S: largest size
-.TP
-\(bu
-t: smallest time
-.TP
-\(bu
-T: largest time
-.TP
-\(bu
-b: smallest bandwidth
-.TP
-\(bu
-B: largest bandwidth
-.LP
-.RE
-.IP
-
-.TP
-\fBmaxdumps\fR int
-Default: 1\&. The maximum number of backups from a single host that \fBAMANDA\fR will attempt to run in parallel\&. See also the \fBinparallel\fR option\&.
-
-Note that this parameter may also be set in a specific \fBdumptype\fR (see below)\&. This value sets the default for all \fBdumptype\fRs so must appear in \fBamanda\&.conf\fR before any \fBdumptype\fRs are defined\&.
-
-.TP
-\fBbumpsize\fR int
-Default: \fB10 Mbytes\fR\&. The minimum savings required to trigger an automatic bump from one incremental level to the next\&. If \fBAMANDA\fR 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 \fBbumpmult\fR option\&.
-
-.TP
-\fBbumpmult\fR \fB float\fR
-Default: 1\&.5\&. The bump size multiplier\&. \fBAMANDA\fR multiplies \fBbumpsize\fR 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 \fBbumpsize\fR and \fBbumpmult\fR 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\&.
-
-.TP
-\fBbumpdays\fR \fB int\fR
-Default: \fB2 days\fR\&. To insure redundancy in the dumps, \fBAMANDA\fR keeps filesystems at the same incremental level for at least \fBbumpdays\fR days, even if the other bump threshold criteria are met\&.
-
-.TP
-\fBdiskfile\fR \fB string\fR
-Default: \fBdisklist\fR\&. The file name for the \fBdisklist\fR file holding client hosts, disks and other client dumping information\&.
-
-.TP
-\fBinfofile\fR \fB string\fR
-Default: \fI/usr/adm/amanda/curinfo\fR\&. The file or directory name for the historical information database\&. If \fBAMANDA\fR was configured to use DBM databases, this is the base file name for them\&. If it was configured to use text formated databases (the default), this is the base directory and within here will be a directory per client, then a directory per disk, then a text file of data\&.
-
-.TP
-\fBlogdir\fR \fB string\fR
-Default: \fI/usr/adm/amanda\fR\&. The directory for the \fBamdump\fR and \fBlog\fR files\&.
-
-.TP
-\fBindexdir\fR \fB string\fR
-Default \fI/usr/adm/amanda/index\fR\&. The directory where index files (backup image catalogues) are stored\&. Index files are only generated for filesystems whose \fBdumptype\fR has the \fBindex\fR option enabled\&.
-
-.TP
-\fBtapelist\fR \fB string\fR
-Default: \fBtapelist\fR\&. The file name for the active \fBtapelist\fR file\&. \fBAMANDA\fR maintains this file with information about the active set of tapes\&.
-
-.TP
-\fBtapebufs\fR \fB int\fR
-Default: 20\&. The number of buffers used by the \fBtaper\fR process run by \fBamdump\fR and \fBamflush\fR to hold data as it is read from the network or disk before it is written to tape\&. Each buffer is a little larger than 32 KBytes and is held in a shared memory region\&.
-
-.TP
-\fBreserve\fR \fB number\fR
-Default: 100\&. The part of holding\-disk space that should be reserved for incremental backups if no tape is available, expressed as a percentage of the available holding\-disk space (0\-100)\&. By default, when there is no tape to write to, degraded mode (incremental) backups will be performed to the holding disk\&. If full backups should also be allowed in this case, the amount of holding disk space reserved for incrementals should be lowered\&.
-
-.TP
-\fBautoflush\fR \fB bool\fR
-Default: \fBoff\fR\&. Whether an amdump run will flush the dump already on holding disk to tape\&.
-
-.TP
-\fBamrecover_do_fsf\fR \fB bool\fR
-Default: \fBoff\fR\&. Amrecover will call amrestore with the \-f flag for faster positioning of the tape\&.
-
-.TP
-\fBamrecover_check_label\fR \fB bool\fR
-Default: \fBoff\fR\&. Amrecover will call amrestore with the \-l flag to check the label\&.
-
-.TP
-\fBamrecover_changer\fR \fB string\fR
-Default: ''\&. Amrecover will use the changer if you use 'settape <string>' and that string is the same as the amrecover_changer setting\&.
-
-.TP
-\fBcolumnspec\fR \fB string\fR
-Defines the width of columns \fBamreport\fR should use\&. \fBString\fR is a comma (',') separated list of triples\&. Each triple consists of three parts which are separated by a equal sign ('=') and a colon (':') (see the example)\&. These three parts specify:
-
-
-.RS
-.TP 3
-\(bu
-the name of the column, which may be:
-
-.RS
-.TP 3
-\(bu
-Compress (compression ratio)
-.TP
-\(bu
-Disk (client disk name)
-.TP
-\(bu
-DumpRate (dump rate in KBytes/sec)
-.TP
-\(bu
-DumpTime (total dump time in hours:minutes)
-.TP
-\(bu
-HostName (client host name)
-.TP
-\(bu
-Level (dump level)
-.TP
-\(bu
-OrigKB (original image size in KBytes)
-.TP
-\(bu
-OutKB (output image size in KBytes)
-.TP
-\(bu
-TapeRate (tape writing rate in KBytes/sec)
-.TP
-\(bu
-TapeTime (total tape time in hours:minutes)
-.LP
-.RE
-.IP
-.TP
-\(bu
-the amount of space to display before the column (used to get whitespace between columns)\&.
-.TP
-\(bu
-the width of the column itself\&. If set to a negative value, the width will be calculated on demand to fit the largest entry in this column\&.
-.LP
-.RE
-.IP
-Here is an example:
-
-.nf
-
-columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"
-.fi
-The above will display the disk information in 18 characters and put one space before it\&. The hostname column will be 10 characters wide with no space to the left\&. The output KBytes column is seven characters wide with one space before it\&.
-
-.TP
-\fBincludefile\fR \fB string\fR
-Default: \fBnone\fR\&. The name of an \fBAMANDA\fR configuration file to include within the current file\&. Useful for sharing dumptypes, tapetypes and interface definitions among several configurations\&.
-
-.SH "HOLDINGDISK SECTION"
-