+\fBprinter\fR \fIstring\fR
+.RS 4
+Printer to use when doing tape labels\&. See the
+\fBlbl\-templ\fR
+\fBtapetype\fR
+option\&.
+.RE
+.PP
+\fBtapedev\fR \fIstring\fR
+.RS 4
+Default:
+\fI"null:"\fR\&. This parameter can either specify a device (explicitly or by referencing a device definition \- see
+\fBamanda-devices\fR(7)) or a tape changer (explicitly or by referencing a device definition \- see
+\fBamanda-changers\fR(7))\&.
+.RE
+.PP
+\fBdevice\-property\fR \fIstring\fR \fIstring\fR
+.RS 4
+These options can set various device properties\&. See
+\fBamanda-devices\fR(7)
+for more information on device properties and their syntax\&. Both strings are always quoted; the first string contains the name of the property to set, and the second contains its value\&. For example, to set a fixed block size of 128k, write:
+.nf
+device\-property "BLOCK_SIZE" "128k"
+.fi
+.RE
+.PP
+\fBproperty\fR [\fBappend\fR] \fIstring\fR \fIstring\fR+
+.RS 4
+These options can set various properties, they can be used by third party software to store information in the configuration file\&. Both strings are quoted; the first string contains the name of the property to set, and the others contains its values\&.
+\fBappend\fR
+keyword append the values to the list of values for that property\&.
+.RE
+.PP
+\fBtpchanger\fR \fIstring\fR
+.RS 4
+Default: not set\&. The tape changer to use\&. In most cases, only one of
+\fBtpchanger\fR
+or
+\fBtapedev\fR
+is specified, although for backward compatibility both may be specified if
+\fBtpchanger\fR
+gives the name of an old changer script\&. See
+\fBamanda-changers\fR(7)
+for more information on configuring changers\&.
+.RE
+.PP
+\fBinteractivity\fR \fIstring\fR
+.RS 4
+Default: not set\&. The interactivity module Amanda should use to interact with the user\&. See
+\fBamanda-interactivity\fR(7)
+for a list of modules\&.
+.RE
+.PP
+\fBtaperscan\fR \fIstring\fR
+.RS 4
+Default: traditional\&. The taperscan module amanda should use to find a tape to write to\&. See
+\fBamanda-taperscan\fR(7)
+for a list of modules\&.
+.RE
+.PP
+\fBchangerdev\fR \fIstring\fR
+.RS 4
+Default:
+\fI"dev/null"\fR\&. A tape changer configuration parameter\&. Usage depends on the particular changer defined with the
+\fBtpchanger\fR
+option\&.
+.RE
+.PP
+\fBchangerfile\fR \fIstring\fR
+.RS 4
+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\&.
+.RE
+.PP
+\fBruntapes\fR \fIint\fR
+.RS 4
+Default:
+\fI1\fR\&. 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\&.
+.sp
+If a tape changer is configured, this may be set larger than one to let Amanda write to more than one tape\&.
+.sp
+Note that this is an upper bound on the number of tapes, and Amanda may use less\&.
+.RE
+.PP
+\fBmaxdumpsize\fR \fIint\fR
+.RS 4
+Default:
+\fI\fBruntapes\fR\fR\fI*\fR\fI\fBtape\-length\fR\fR\&. Maximum number of bytes the planner will schedule for a run\&.
+.sp
+The default unit is Kbytes if it is not specified\&.
+.RE
+.PP
+\fBtaperalgo\fR [ \fBfirst\fR | \fBfirstfit\fR | \fBlargest\fR | \fBlargestfit\fR | \fBsmallest\fR | \fBlast\fR ]
+.RS 4
+Default:
+\fBfirst\fR\&. The algorithm used to choose which dump image to send to the taper\&.
+.PP
+\fBfirst\fR
+.RS 4
+First in, first out\&.
+.RE
+.PP
+\fBfirstfit\fR
+.RS 4
+The first dump image that will fit on the current tape\&.
+.RE
+.PP
+\fBlargest\fR
+.RS 4
+The largest dump image\&.
+.RE
+.PP
+\fBlargestfit\fR
+.RS 4
+The largest dump image that will fit on the current tape\&.
+.RE
+.PP
+\fBsmallest\fR
+.RS 4
+The smallest dump image\&.
+.RE
+.PP
+\fBlast\fR
+.RS 4
+Last in, first out\&.
+.RE
+.RE
+.PP
+\fBtaper\-parallel\-write\fR \fIint\fR
+.RS 4
+Default:
+\fI1\fR\&. Amanda can write simultaneously up to that number of volume at any given time\&. The changer must have as many drives\&.
+.RE
+.PP
+\fBeject\-volume\fR \fIint\fR
+.RS 4
+Default:
+\fIno\fR\&. Set to
+\fByes\fR
+if you want the volume to be ejected after Amanda wrote data to it\&. It works only with some changer and device\&.
+.RE
+.PP
+\fBlabelstr\fR \fIstring\fR
+.RS 4
+Default:
+\fI"\&.*"\fR\&. The tape label constraint regular expression\&. All tape labels generated (see
+\fBamlabel\fR(8)) 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, "DAILY[0\-9][0\-9]*" vs\&. "ARCHIVE[0\-9][0\-9]*") to avoid overwriting each other\*(Aqs tapes\&.
+.RE
+.PP
+\fBtapetype\fR \fIstring\fR
+.RS 4
+Default:
+\fIno default\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\&.
+.RE
+.PP
+\fBctimeout\fR \fIint\fR
+.RS 4
+Default:
+\fI30 seconds\fR\&. Maximum amount of time that
+\fBamcheck\fR
+will wait for each client host\&.
+.RE
+.PP
+\fBdtimeout\fR \fIint\fR
+.RS 4
+Default:
+\fI1800 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\&.
+.RE
+.PP
+\fBetimeout\fR \fIint\fR
+.RS 4
+Default:
+\fI300 seconds\fR\&. Amount of time per estimate on a given client that the
+\fBplanner\fR
+step of
+\fBamdump\fR
+will wait to get the dump size estimates (note: Amanda runs up to 3 estimates for each DLE)\&. For instance, with the default of 300 seconds and four DLE\*(Aqs, each estimating level 0 and level 1 on client A,
+\fBplanner\fR
+will wait up to 40 minutes for that machine\&. A negative value will be interpreted as a total amount of time to wait per client instead of per disk\&.
+.RE
+.PP
+\fBconnect\-tries\fR \fIint\fR
+.RS 4
+Default:
+\fI3\fR\&. How many times the server will try a connection\&.
+.RE
+.PP
+\fBreq\-tries\fR \fIint\fR
+.RS 4
+Default:
+\fI3\fR\&. How many times the server will resend a REQ packet if it doesn\*(Aqt get the ACK packet\&.
+.RE
+.PP
+\fBnetusage\fR \fIint\fR
+.RS 4
+Default:
+\fI80000 Kbps\fR\&. The maximum network bandwidth allocated to Amanda, in Kbytes per second\&. See also the
+\fBinterface\fR
+section\&.
+.RE
+.PP
+\fBinparallel\fR \fIint\fR
+.RS 4
+Default:
+\fI10\fR\&. 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\*(Aqt 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\&.
+.RE
+.PP
+\fBdisplayunit\fR "k|m|g|t"
+.RS 4
+Default:
+\fI"k"\fR\&. The unit used to print many numbers, k=kilo, m=mega, g=giga, t=tera\&.
+.RE
+.PP
+\fBdumporder\fR \fIstring\fR
+.RS 4
+Default:
+\fI"tttTTTTTTT"\fR\&. The priority order of each dumper:
+.sp
+.nf
+s: smallest size
+S: largest size
+t: smallest time
+T: largest time
+b: smallest bandwidth
+B: largest bandwidth
+.fi
+.RE
+.PP
+\fBmaxdumps\fR \fIint\fR
+.RS 4
+Default:
+\fI1\fR\&. The maximum number of backups from a single host that Amanda will attempt to run in parallel\&. See also the
+\fBinparallel\fR
+option\&.
+.sp
+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\&.
+.RE
+.PP
+\fBbumpsize\fR \fIint\fR
+.RS 4
+Default:
+\fI10 Mbytes\fR\&. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as size\&. If Amanda determines that the next higher backup level will be this much smaller than the current level, it will do the next level\&. The value of this parameter is used only if the parameter
+\fIbumppercent\fR
+is set to 0\&.
+.sp
+The default unit is Kbytes if it is not specified\&.
+.sp
+The global setting of this parameter can be overwritten inside of a dumptype\-definition\&.
+.sp
+See also the options
+\fBbumppercent\fR,
+\fBbumpmult\fR
+and
+\fBbumpdays\fR\&.
+.RE
+.PP
+\fBbumppercent\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. The minimum savings required to trigger an automatic bump from one incremental level to the next, expressed as percentage of the current size of the DLE (size of current level 0)\&. If Amanda determines that the next higher backup level will be this much smaller than the current level, it will do the next level\&.
+.sp
+If this parameter is set to 0, the value of the parameter
+\fIbumpsize\fR
+is used to trigger bumping\&.
+.sp
+The global setting of this parameter can be overwritten inside of a dumptype\-definition\&.
+.sp
+See also the options
+\fBbumpsize\fR,
+\fBbumpmult\fR
+and
+\fBbumpdays\fR\&.
+.RE
+.PP
+\fBbumpmult\fR \fIfloat\fR
+.RS 4
+Default:
+\fI1\&.5\fR\&. The bump size multiplier\&. Amanda 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\&.
+.sp
+The global setting of this parameter can be overwritten inside of a dumptype\-definition\&.
+.RE
+.PP
+\fBbumpdays\fR \fIint\fR
+.RS 4
+Default:
+\fI2 days\fR\&. To insure redundancy in the dumps, Amanda keeps filesystems at the same incremental level for at least
+\fBbumpdays\fR
+days, even if the other bump threshold criteria are met\&.
+.sp
+The global setting of this parameter can be overwritten inside of a dumptype\-definition\&.
+.RE
+.PP
+\fBdiskfile\fR \fIstring\fR
+.RS 4
+Default:
+\fI"disklist"\fR\&. The file name for the
+\fIdisklist\fR
+file holding client hosts, disks and other client dumping information\&.
+.RE
+.PP
+\fBinfofile\fR \fIstring\fR
+.RS 4
+Default:
+\fI"/usr/adm/amanda/curinfo"\fR\&. The file or directory name for the historical information database\&. If Amanda 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\&.
+.RE
+.PP
+\fBlogdir\fR \fIstring\fR
+.RS 4
+Default:
+\fI"/usr/adm/amanda"\fR\&. The directory for the
+\fBamdump\fR
+and
+\fBlog\fR
+files\&.
+.RE
+.PP
+\fBindexdir\fR \fIstring\fR
+.RS 4
+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\&.
+.RE
+.PP
+\fBtapelist\fR \fIstring\fR
+.RS 4
+Default:
+\fI"tapelist"\fR\&. The file name for the active
+\fBtapelist\fR(5)\&. Amanda maintains this file with information about the active set of tapes\&.
+.RE
+.PP
+\fBdevice\-output\-buffer\-size\fR \fIint\fR
+.RS 4
+Default:
+\fI1280k\fR\&. Controls the amount of memory used by Amanda to hold data as it is read from the network or disk before it is written to the output device\&. Higher values may be useful on fast tape drives and optical media\&.
+.sp
+The default unit is bytes if it is not specified\&.
+.RE
+.PP
+\fBtapebufs\fR \fIint\fR
+.RS 4
+Default:
+\fI20\fR\&. This option is deprecated; use the
+\fBdevice\-output\-buffer\-size\fR
+directive instead\&.
+\fBtapebufs\fR
+works the same way, but the number specified is multiplied by the device blocksize prior to use\&.
+.RE
+.PP
+\fBreserve\fR \fIint\fR
+.RS 4
+Default:
+\fI100\fR\&. 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\&.
+.RE
+.PP
+\fBautoflush\fR \fBno\fR|\fByes\fR|\fBall\fR
+.RS 4
+Default:
+\fBno\fR\&. Whether an amdump run will flush the dumps from holding disk to tape\&. With
+\fByes\fR, only dump matching the command line argument are flushed\&. With
+\fBall\fR, all dump are flushed\&.
+.RE
+.PP
+\fBamrecover\-do\-fsf\fR \fIbool\fR
+.RS 4
+Deprecated; amrecover always uses fsf, and does not invoke amrestore\&.
+.sp
+Default:
+\fBon\fR\&. Amrecover will call amrestore with the \-f flag for faster positioning of the tape\&.
+.RE
+.PP
+\fBamrecover\-check\-label\fR \fIbool\fR
+.RS 4
+Deprecated; amrecover always checks the label, and does not invoke amrestore\&.
+.sp
+Default:
+\fBon\fR\&. Amrecover will call amrestore with the \-l flag to check the label\&.
+.RE
+.PP
+\fBamrecover\-changer\fR \fIstring\fR
+.RS 4
+Default: not set\&. Amrecover will use the changer if you use \*(Aqsettape <string>\*(Aq and that string is the same as the
+\fBamrecover\-changer\fR
+setting\&.
+.RE
+.PP
+\fBcolumnspec\fR \fIstring\fR
+.RS 4
+default: "HostName=0:12:12,Disk=1:11:11,Level=1:1:1,OrigKB=1:\-7:0,OutKB=1:\-7:0,Compress=1:\-6:1,DumpTime=1:\-7:7,Dumprate=1:\-6:1,TapeTime=1:\-6:6,TapeRate=1:\-6:1"
+.sp
+Defines the width of columns
+\fBamreport\fR
+should use\&.
+\fIString\fR
+is a comma (\*(Aq,\*(Aq) separated list of triples\&. Each triple consists of three parts which are separated by a equal sign (\*(Aq=\*(Aq) and a colon (\*(Aq:\*(Aq) (see the example)\&. These four parts specify:
+.sp
+.RS 4
+.ie n \{\
+\h'-04' 1.\h'+01'\c
+.\}
+.el \{\
+.sp -1
+.IP " 1." 4.2
+.\}
+the name of the column, which may be:
+.sp
+.nf
+ Compress (compression ratio)
+ Disk (client disk name)
+ DumpRate (dump rate in KBytes/sec)
+ DumpTime (total dump time in hours:minutes)
+ HostName (client host name)
+ Level (dump level)
+ OrigKB (original image size in KBytes)
+ OutKB (output image size in KBytes)
+ TapeRate (tape writing rate in KBytes/sec)
+ TapeTime (total tape time in hours:minutes)
+.fi
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04' 2.\h'+01'\c
+.\}
+.el \{\
+.sp -1
+.IP " 2." 4.2
+.\}
+the amount of space to display before the column (used to get whitespace between columns)\&.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04' 3.\h'+01'\c
+.\}
+.el \{\
+.sp -1
+.IP " 3." 4.2
+.\}
+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\&.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04' 4.\h'+01'\c
+.\}
+.el \{\
+.sp -1
+.IP " 4." 4.2
+.\}
+the precision of the column, number of digit after the decimal point for number\&.
+.RE
+.sp
+Here is an example:
+.sp
+.nf
+columnspec "Disk=1:18,HostName=0:10,OrigKB=::2,OutKB=1:7"
+.fi
+.sp
+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 Original KBytes print 2 decimal digit\&. The output KBytes column is seven characters wide with one space before it\&.
+.RE
+.PP
+\fBincludefile\fR \fIstring\fR
+.RS 4
+Default:
+\fIno default\fR\&. The name of an Amanda configuration file to include within the current file\&. Useful for sharing dumptypes, tapetypes and interface definitions among several configurations\&. Relative pathnames are relative to the configuration directory\&.
+.RE
+.PP
+\fBdebug\-days\fR \fIint\fR
+.RS 4
+Default:
+\fI3\fR\&. The number of days the debug files are kept\&.
+.RE
+.PP
+\fBdebug\-auth\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Debug level of the auth module
+.RE
+.PP
+\fBdebug\-event\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Debug level of the event module
+.RE
+.PP
+\fBdebug\-holding\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Debug level of the holdingdisk module
+.RE
+.PP
+\fBdebug\-protocol\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Debug level of the protocol module
+.RE
+.PP
+\fBdebug\-planner\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Debug level of the planner process
+.RE
+.PP
+\fBdebug\-driver\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Debug level of the driver process
+.RE
+.PP
+\fBdebug\-dumper\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Debug level of the dumper process
+.RE
+.PP
+\fBdebug\-chunker\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Debug level of the chunker process
+.RE
+.PP
+\fBdebug\-taper\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Debug level of the taper process
+.RE
+.PP
+\fBdebug\-recovery\fR \fIint\fR
+.RS 4
+Default:
+\fI1\fR\&. Debug level of all recovery process
+.RE
+.PP
+\fBflush\-threshold\-dumped\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Amanda will not begin writing data to a new volume until the amount of data on the holding disk is at least this percentage of the volume size\&. In other words, Amanda will not begin until the amount of data on the holding disk is greater than the tape length times this parameter\&. This parameter may be larger than 100%, for example to keep more recent dumps on the holding disk for faster recovery\&.
+.sp
+Needless to say, your holding disk must be big enough that this criterion could be satisfied\&. If the holding disk cannot be used for a particular dump (because, for example, there is no remaining holding space) then Amanda will disregard the constraint specified by this setting and start a new volume anyway\&. Once writing to a volume has begun, this constraint is not applied unless and until a new volume is needed\&.
+.sp
+The value of this parameter may not exceed than that of the
+\fBflush\-threshold\-scheduled\fR
+parameter\&.
+.RE
+.PP
+\fBflush\-threshold\-scheduled\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. Amanda will not begin writing data to a new volume until the sum of the amount of data on the holding disk and the estimated amount of data remaining to be dumped during this run is at least this percentage of the volume size\&. In other words, Amanda will not begin until the inequality
+h + s > t \(mu d
+is satisfied, where
+h
+is the amount of data on the holding disk,
+s
+is the total amount of data scheduled for this run but not dumped yet,
+t
+is the capacity of a volume, and
+d
+is this parameter, expressed as a percentage\&. This parameter may be larger than 100%\&.
+.sp
+Needless to say, your holding disk must be big enough that this criterion could be satisfied\&. If the holding disk cannot be used for a particular dump (because, for example, there is no remaining holding space) then Amanda will disregard the constraint specified by this setting and start a new volume anyway\&. Once writing to a volume has begun, this constraint is not applied unless and until a new volume is needed\&.
+.sp
+The value of this parameter may not be less than that of the
+\fBflush\-threshold\-dumped\fR
+or
+\fBtaperflush\fR
+parameters\&.
+.RE
+.PP
+\fBtaperflush\fR \fIint\fR
+.RS 4
+Default:
+\fI0\fR\&. At the end of a run, Amanda will start a new tape to flush remaining data if there is more data on the holding disk at the end of a run than this setting allows; the amount is specified as a percentage of the capacity of a single volume\&. In other words, at the end of a run, Amanda will begin a new tape if the inequality
+h > t \(mu f
+is satisfied, where
+h
+is the amount of data remaining on the holding disk from this or previous runs,
+t
+is the capacity of a volume, and
+f
+is this parameter, expressed as a percentage\&. This parameter may be greater than 100%\&.
+.sp
+The value of this parameter may not exceed that of the
+\fBflush\-threshold\-scheduled\fR
+parameter\&.;
+\fBautoflush\fR
+must be set to \*(Aqyes\*(Aq if
+\fBtaperflush\fR
+is greater than 0\&.
+.RE
+.PP
+\fBreserved\-udp\-port\fR \fIint\fR,\fIint\fR
+.RS 4
+Default: \-\-with\-udpportrange or
+\fI512,1023\fR\&. Reserved udp port that will be used (bsd, bsdudp)\&. Range is inclusive\&.
+.RE
+.PP
+\fBreserved\-tcp\-port\fR \fIint\fR,\fIint\fR
+.RS 4
+Default: \-\-with\-low\-tcpportrange or
+\fI512,1023\fR\&. Reserved tcp port that will be used (bsdtcp)\&. Range is inclusive\&.
+.RE
+.PP
+\fBunreserved\-tcp\-port\fR \fIint\fR,\fIint\fR
+.RS 4
+Default: \-\-with\-tcpportrange or
+\fI1024,65535\fR\&. Unreserved tcp port that will be used (bsd, bsdudp)\&. Range is inclusive\&.
+.RE
+.PP
+\fBrecovery\-limit\fR [ \fIstring\fR | \fBsame\-host\fR | \fBserver\fR]
+.RS 4
+Default: none (no limitations)\&. This parameter limits the hosts that may do recoveries\&. Hosts are identified by their authenticated peer name, as described in
+\fBamanda-auth\fR(7); if this is not available and the recovery\-limit parameter is present, recovery will be denied\&. The arguments to the parameter are strings giving host match expressions (see
+\fBamanda-match\fR(7)) or the special keywords
+\fBsame\-host\fR
+or
+\fBserver\fR\&. The
+\fBsame\-host\fR
+keyword requires an exact match to the hostname of the DLE being recovered\&. The
+\fBserver\fR
+keyword require the connection come from the fqdn of the server\&. Specifying no arguments at all will disable all recoveries from any host\&.
+.sp
+Note that match expressions can be constructed to be forgiving of e\&.g\&., fully\-qualified vs\&. unqualified hostnames, but
+\fBsame\-host\fR
+requires an exact match\&.
+.sp
+The error messages that appear in amrecover are intentionally vague to avoid information leakage\&. Consult the amindexd debug log for more details on the reasons a recovery was rejected\&.
+.sp
+Recovery limits can be refined on a per\-DLE basis using the dumptype parameter of the same name\&. Note that the default value will apply to any dumpfiles for disks which no longer appear in the disklist; thus leaving the global parameter at its default value but setting it for all DLEs is not sufficient to maintain secure backups\&.
+.RE
+.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
+define holdingdisk \fIname\fR {
+ \fIholdingdisk\-option\fR \fIholdingdisk\-value\fR
+ \&.\&.\&.
+}
+.fi
+.PP
+The { must appear at the end of a line, and the } on its own line\&.
+.PP
+\fIName\fR
+is a logical name for this holding disk\&.
+.PP
+The options and values are:
+.PP
+\fBcomment\fR \fIstring\fR
+.RS 4
+Default: not set\&. A comment string describing this holding disk\&.
+.RE
+.PP
+\fBdirectory\fR \fIstring\fR
+.RS 4
+Default:
+\fI"/dumps/amanda"\fR\&. The path to this holding area\&.
+.RE
+.PP
+\fBuse\fR \fIint\fR
+.RS 4
+Default:
+\fI0 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, Amanda will use all available space minus that value\&.
+.RE
+.PP
+\fBchunksize\fR \fIint\fR
+.RS 4
+Default:
+\fI1 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\&.
+.sp
+The default unit is Kbytes if it is not specified\&.
+.sp
+If 0 is specified, Amanda will create holding disk chunks as large as ((INT_MAX/1024)\-64) Kbytes\&.
+.sp
+Each holding disk chunk includes a 32 Kbyte header, so the minimum chunk size is 64 Kbytes (but that would be really silly)\&.
+.sp
+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 Amanda 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\&.
+.RE
+.SH "DUMPTYPE SECTION"
+.PP
+The
+\fBamanda.conf\fR(5)
+file may define multiple sets of backup options and refer to them by name from the
+\fBdisklist\fR(5)
+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 "\fIname\fR" {
+ \fIdumptype\-option\fR \fIdumptype\-value\fR
+ \&.\&.\&.
+}
+.fi
+.PP
+The { must appear at the end of a line, and the } on its own line\&.
+.PP
+\fIName\fR
+is the name of this set of backup options\&. It is referenced from the
+\fBdisklist\fR(5)
+file\&.
+.PP
+Some of the options in a
+\fBdumptype\fR
+section are the same as those in the main part of
+\fBamanda.conf\fR(5)\&. 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\&.