-.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"
-
-.PP
-The \fBamanda\&.conf\fR file may define one or more holding disks used as buffers to hold backup images before they are written to tape\&. The syntax is:
-.nf
-
-holdingdisk \fBname\fR {
- \fBholdingdisk\-option\fR \fBholdingdisk\-value\fR
- \&.\&.\&.
-}
-.fi
-
-.PP
-\fBName\fR is a logical name for this holding disk\&.
-
-.PP
-The options and values are:
-
-.TP
-\fBcomment\fR \fB string\fR
-Default: \fBnone\fR\&. A comment string describing this holding disk\&.
-
-.TP
-\fBdirectory\fR \fB disk\fR
-Default: \fI/dumps/amanda\fR\&. The path to this holding area\&.
-
-.TP
-\fBuse\fR \fB int\fR
-Default: \fB0 Gb\fR\&. Amount of space that can be used in this holding disk area\&. If the value is zero, all available space on the file system is used\&. If the value is negative, \fBAMANDA\fR will use all available space minus that value\&.
-
-.TP
-\fBchunksize\fR \fB int\fR
-Default: \fB1 Gb\fR\&. Holding disk chunk size\&. Dumps larger than the specified size will be stored in multiple holding disk files\&. The size of each chunk will not exceed the specified value\&. However, even though dump images are split in the holding disk, they are concatenated as they are written to tape, so each dump image still corresponds to a single continuous tape section\&.
-
-If 0 is specified, \fBAMANDA\fR will create holding disk chunks as large as ((INT_MAX/1024)\-64) Kbytes\&.
-
-Each holding disk chunk includes a 32 Kbyte header, so the minimum chunk size is 64 Kbytes (but that would be really silly)\&.
-
-Operating systems that are limited to a maximum file size of 2 Gbytes actually cannot handle files that large\&. They must be at least one byte less than 2 Gbytes\&. Since \fBAMANDA\fR works with 32 Kbyte blocks, and to handle the final read at the end of the chunk, the chunk size should be at least 64 Kbytes (2 * 32 Kbytes) smaller than the maximum file size, e\&.g\&. 2047 Mbytes\&.
-
-.SH "DUMPTYPE SECTION"
-
-.PP
-The \fBamanda\&.conf\fR file may define multiple sets of backup options and refer to them by name from the \fBdisklist\fR file\&. For instance, one set of options might be defined for file systems that can benefit from high compression, another set that does not compress well, another set for file systems that should always get a full backup and so on\&.
-
-.PP
-A set of backup options are entered in a \fBdumptype\fR section, which looks like this:
-.nf
-
-define dumptype \fBname\fR {
- \fBdumptype\-option\fR \fBdumptype\-value\fR
- \&.\&.\&.
-}
-.fi
-
-.PP
-\fBName\fR is the name of this set of backup options\&. It is referenced from the \fBdisklist\fR file\&.
-
-.PP
-Some of the options in a \fBdumptype\fR section are the same as those in the main part of \fBamanda\&.conf\fR\&. The main option value is used to set the default for all \fBdumptype\fR sections\&. For instance, setting \fBdumpcycle\fR to 50 in the main part of the config file causes all following \fBdumptype\fR sections to start with that value, but the value may be changed on a section by section basis\&. Changes to variables in the main part of the config file must be done before (earlier in the file) any \fBdumptype\fRs are defined\&.
-
-.PP
-The dumptype options and values are:
-
-.TP
-\fBauth\fR \fB string\fR
-Default: \fBbsd\fR\&. Type of authorization to perform between tape server and backup client hosts\&. May be \fBkrb4\fR to use Kerberos\-IV authorization\&.
-
-.TP
-\fBcomment\fR \fB string\fR
-Default: \fBnone\fR\&. A comment string describing this set of backup options\&.
-
-.TP
-\fBcomprate\fR \fBfloat\fR [, \fBfloat\fR ]
-Default: 0\&.50, 0\&.50\&. The expected full and incremental compression factor for dumps\&. It is only used if \fBAMANDA\fR does not have any history information on compression rates for a filesystem, so should not usually need to be set\&. However, it may be useful for the first time a very large filesystem that compresses very little is backed up\&.
-
-.TP
-\fBcompress [client|server]\fR \fB string\fR
-Default: \fBclient fast\fR\&. If \fBAMANDA\fR does compression of the backup images, it can do so either on the backup client host before it crosses the network or on the tape server host as it goes from the network into the holding disk or to tape\&. Which place to do compression (if at all) depends on how well the dump image usually compresses, the speed and load on the client or server, network capacity, holding disk capacity, availability of tape hardware compression, etc\&.
-
-For either type of compression, \fBAMANDA\fR also allows the selection of two styles of compression\&. \fBBest\fR is the best compression available, often at the expense of CPU overhead\&. \fBFast\fR is often not as good a compression as \fBbest\fR, but usually less CPU overhead\&.
-
-So the \fBcompress\fR options line may be one of:
-
-
-.RS
-.TP 3
-\(bu
-compress none
-.TP
-\(bu
-compress [client] fast
-.TP
-\(bu
-compress [client] best
-.TP
-\(bu
-compress server fast
-.TP
-\(bu
-compress server best
-.LP
-.RE
-.IP
-Note that some tape devices do compression and this option has nothing to do with whether that is used\&. If hardware compression is used (usually via a particular tape device name or \fBmt\fR option), \fBAMANDA\fR (software) compression should be disabled\&.
-
-.TP
-\fBdumpcycle\fR \fB int\fR
-Default: \fB10 days\fR\&. The number of days in the backup cycle\&. Each disk using this set of options will get a full backup at least this often\&. Setting this to zero tries to do a full backup each run\&.
-
-.TP
-\fBexclude\fR [ \fBlist|file\fR ][[optional][ \fBappend\fR ][ \fB string\fR ]+]
-Default: \fBfile\fR\&. There are two exclude lists, \fBexclude file\fR and \fBexclude list\&.\fR With \fBexclude file\fR , the \fBstring\fR is a \fBGNU\-tar\fR exclude expression\&. With \fBexclude list\fR , the \fBstring\fR is a file name on the client containing \fBGNU\-tar\fR exclude expressions\&.
-
-All exclude expressions are concatenated in one file and passed to \fBGNU\-tar\fR as an \fB\-\-exclude\-from\fR argument\&.
-
-With the \fBappend\fR keyword, the \fBstring\fR is appended to the current list, without it, the \fBstring\fR overwrites the list\&.
-
-If \fBoptional\fR is specified for \fBexclude list\fR, then amcheck will not complain if the file doesn't exist or is not readable\&.
-
-For \fBexclude list\fR, if the file name is relative, the disk name being backed up is prepended\&. So if this is entered:
-
-.nf
-
- exclude list ``\fB\&.amanda\&.excludes\fR''
-.fi
-the actual file used would be \fI/var/\&.amanda\&.excludes\fR for a backup of \fI/var\fR, \fI/usr/local/\&.amanda\&.excludes\fR for a backup of \fI/usr/local\fR, and so on\&.
-
-.TP
-\fBholdingdisk\fR \fB boolean\fR
-Default: \fByes\fR\&. Whether a holding disk should be used for these backups or whether they should go directly to tape\&. If the holding disk is a portion of another file system that \fBAMANDA\fR is backing up, that file system should refer to a dumptype with \fBholdingdisk\fR set to \fBno\fR to avoid backing up the holding disk into itself\&.
-
-.TP
-\fBignore\fR \fB boolean\fR
-Default: \fBno\fR\&. Whether disks associated with this backup type should be backed up or not\&. This option is useful when the \fBdisklist\fR file is shared among several configurations, some of which should not back up all the listed file systems\&.
-
-.TP
-\fBinclude\fR [ \fBlist|file\fR ][[optional][ \fBappend\fR ][ \fB string\fR ]+]
-Default: \fBfile\fR "\&."\&. There are two include lists, \fBinclude file\fR and \fBinclude list\&.\fR With \fBinclude file\fR , the \fBstring\fR is a glob expression\&. With \fBinclude list\fR , the \fBstring\fR is a file name on the client containing glob expressions\&.
-
-All include expressions are expanded by \fBAMANDA\fR, concatenated in one file and passed to \fBGNU\-tar\fR as a \fB\-\-files\-from\fR argument\&. They must start with "\&./" and contain no other "/"\&.
-
-With the \fBappend\fR keyword, the \fBstring\fR is appended to the current list, without it, the \fBstring\fR overwrites the list\&.
-
-If \fBoptional\fR is specified for \fBinclude list,\fR then amcheck will not complain if the file doesn't exist or is not readable\&.
-
-For \fBinclude list\fR, If the file name is relative, the disk name being backed up is prepended\&.
-
-.TP
-\fBindex\fR \fB boolean\fR
-Default: \fBno\fR\&. Whether an index (catalogue) of the backup should be generated and saved in \fBindexdir\fR\&. These catalogues are used by the \fBamrecover\fR utility\&.
-
-.TP
-\fBkencrypt\fR \fB boolean\fR
-Default: \fBno\fR\&. Whether the backup image should be encrypted by Kerberos as it is sent across the network from the backup client host to the tape server host\&.
-
-.TP
-\fBmaxdumps\fR \fB int\fR
-Default: 1\&. The maximum number of backups from a single host that \fBAMANDA\fR will attempt to run in parallel\&. See also the main section parameter \fBinparallel\fR\&.
-
-.TP
-\fBmaxpromoteday\fR \fB int\fR
-Default: 10000\&. The maximum number of day for a promotion, set it 0 if you don't want promotion, set it to 1 or 2 if your disks get overpromoted\&.
-
-.TP
-\fBpriority\fR \fB string\fR
-Default: \fBmedium\fR\&. When there is no tape to write to, \fBAMANDA\fR will do incremental backups in priority order to the holding disk\&. The priority may be high (2)\&. medium (1), low (0) or a number of your choice\&.
-
-.TP
-\fBprogram\fR \fB string\fR
-Default: \fBDUMP\fR\&. The type of backup to perform\&. Valid values are \fBDUMP\fR for the native operating system backup program, and \fBGNUTAR\fR to use \fBGNU\-tar\fR or to do PC backups using Samba\&.
-
-.TP
-\fBrecord\fR \fB boolean\fR
-Default: \fByes\fR\&. Whether to ask the backup program to update its database (e\&.g\&. \fI/etc/dumpdates\fR for DUMP or \fI/usr/local/var/amanda/gnutar\-lists\fR for GNUTAR) of time stamps\&. This is normally enabled for daily backups and turned off for periodic archival runs\&.
-
-.TP
-\fBskip\-full\fR \fB boolean\fR
-Default: \fBno\fR\&. If \fBtrue\fR and \fBplanner\fR has scheduled a full backup, these disks will be skipped, and full backups should be run off\-line on these days\&. It was reported that \fBAMANDA\fR only schedules level 1 incrementals in this configuration; this is probably a bug\&.
-
-.TP
-\fBskip\-incr\fR \fB boolean\fR
-Default: \fBno\fR\&. If \fBtrue\fR and \fBplanner\fR has scheduled an incremental backup, these disks will be skipped\&.
-
-.TP
-\fBstarttime\fR \fB int\fR
-Default: \fBnone\fR\&. Backups will not start until after this time of day\&. The value should be hh*100+mm, e\&.g\&. 6:30PM (18:30) would be entered as 1830\&.
-
-.TP
-\fBstrategy\fR \fB string\fR
-Default: \fBstandard\fR\&. Strategy to use when planning what level of backup to run next\&. Values are:
-
-.TP
-\fBstandard\fR
-The standard \fBAMANDA\fR schedule\&.
-
-.TP
-\fBnofull\fR
-Never do full backups, only level 1 incrementals\&.
-
-.TP
-\fBnoinc\fR
-Never do incremental backups, only full dumps\&.
-
-.TP
-\fBskip\fR
-Never do backups (useful when sharing the \fBdisklist\fR file)\&.
-
-.TP
-\fBincronly\fR
-Only do incremental dumps\&. \fBamadmin force\fR should be used to tell \fBAMANDA\fR that a full dump has been performed off\-line, so that it resets to level 1\&. It is similar to skip\-full, but with incronly full dumps may be scheduled manually\&. Unfortunately, it appears that \fBAMANDA\fR will perform full backups with this configuration, which is probably a bug\&.