+<amdefault>0</amdefault>.
+Debug level of the taper process</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>flush-threshold-dumped</amkeyword> <amtype>int</amtype></term>
+ <listitem>
+<para>Default: <amdefault>0</amdefault>.
+ 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.</para>
+<para> 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.</para>
+<para> The value of this parameter may not exceed than that of
+ the <amkeyword>flush-threshold-scheduled</amkeyword>
+ parameter.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>flush-threshold-scheduled</amkeyword> <amtype>int</amtype></term>
+ <listitem>
+<para>Default: <amdefault>0</amdefault>.
+ 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 <inlineequation><mathphrase>h + s > t ×
+ d</mathphrase></inlineequation> is satisfied,
+ where <mathphrase>h</mathphrase> is the amount of data on the
+ holding disk, <mathphrase>s</mathphrase> is the total amount of
+ data scheduled for this run but not dumped
+ yet, <mathphrase>t</mathphrase> is the capacity of a volume,
+ and <mathphrase>d</mathphrase> is this parameter, expressed as a
+ percentage. This parameter may be larger than 100%.</para>
+<para> 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.</para>
+<para> The value of this parameter may not be less than that of
+ the <amkeyword>flush-threshold-dumped</amkeyword>
+ or <amkeyword>taperflush</amkeyword> parameters.</para>
+ </listitem>
+ </varlistentry>
+
+<!-- the entity '#215' below is U+00D7 MULTIPLICATION SIGN; the 'times' entity
+ is not as portable as one might hope. -->
+ <varlistentry>
+ <term><amkeyword>taperflush</amkeyword> <amtype>int</amtype></term>
+ <listitem>
+<para>Default: <amdefault>0</amdefault>.
+ 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 <inlineequation><mathphrase>h > t ×
+ f</mathphrase></inlineequation> is satisfied,
+ where <mathphrase>h</mathphrase> is the amount of data remaining on the
+ holding disk from this or previous runs, <mathphrase>t</mathphrase>
+ is the capacity of a volume,
+ and <mathphrase>f</mathphrase> is this parameter, expressed as a
+ percentage. This parameter may be greater than 100%.</para>
+<para> The value of this parameter may not exceed that of
+ the <amkeyword>flush-threshold-scheduled</amkeyword>
+ parameter.; <amkeyword>autoflush</amkeyword> must be set to 'yes' if
+ <amkeyword>taperflush</amkeyword> is greater than 0.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>reserved-udp-port</amkeyword> <amtype>int</amtype>,<amtype>int</amtype></term>
+ <listitem>
+<para>Default: --with-udpportrange or
+<amdefault>512,1023</amdefault>.
+Reserved udp port that will be used (bsd, bsdudp).
+Range is inclusive.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>reserved-tcp-port</amkeyword> <amtype>int</amtype>,<amtype>int</amtype></term>
+ <listitem>
+<para>Default: --with-low-tcpportrange or
+<amdefault>512,1023</amdefault>.
+Reserved tcp port that will be used (bsdtcp).
+Range is inclusive.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>unreserved-tcp-port</amkeyword> <amtype>int</amtype>,<amtype>int</amtype></term>
+ <listitem>
+<para>Default: --with-tcpportrange or
+<amdefault>1024,65535</amdefault>.
+Unreserved tcp port that will be used (bsd, bsdudp).
+Range is inclusive.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>recovery-limit</amkeyword> [ <amtype>string</amtype> | <amkeyword>same-host</amkeyword> ]</term>
+ <listitem>
+<para>Default: none (no limitations). This parameter limits the hosts
+ that may do remote recoveries. Hosts are identified by their authenticated
+ peer name, as described in <manref name="amanda-auth" vol="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 <manref name="amanda-match" vol="7"/>) or the special
+ keyword same-host, which requires an exact match to the hostname of the
+ DLE being recovered. Specifying no arguments at all will disable all
+ recoveries from any host.</para>
+
+<para>Note that match expressions can be constructed to be
+ forgiving of e.g., fully-qualified vs. unqualified hostnames, but
+ <amkeyword>same-host</amkeyword> requires an exact match.</para>
+
+<para>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.</para>
+
+<para>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.</para>
+
+ </listitem>
+ </varlistentry>
+
+</variablelist>
+</refsect1>
+
+<refsect1><title>HOLDINGDISK SECTION</title>
+<para>The <emphasis remap='B'>amanda.conf</emphasis>
+file may define one or more holding disks used as buffers to hold
+backup images before they are written to tape.
+The syntax is:</para>
+
+<programlisting>
+define holdingdisk <emphasis remap='I'>name</emphasis> {
+ <emphasis remap='I'>holdingdisk-option</emphasis> <emphasis remap='I'>holdingdisk-value</emphasis>
+ <literal>...</literal>
+}
+</programlisting>
+
+<para>The { must appear at the end of a line, and the } on its own line.</para>
+<para><emphasis remap='I'>Name</emphasis>
+is a logical name for this holding disk.</para>
+
+<para>The options and values are:</para>
+
+<variablelist remap='TP'>
+ <varlistentry>
+ <term><amkeyword>comment</amkeyword> <amtype>string</amtype></term>
+ <listitem>
+<para>Default: not set.
+A comment string describing this holding disk.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>directory</amkeyword> <amtype>string</amtype></term>
+ <listitem>
+<para>Default:
+<amdefault>"/dumps/amanda"</amdefault>.
+The path to this holding area.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>use</amkeyword> <amtype>int</amtype></term>
+ <listitem>
+<para>Default:
+<amdefault>0 Gb</amdefault>.
+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.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>chunksize</amkeyword> <amtype>int</amtype></term>
+ <listitem>
+<para>Default:
+<amdefault>1 Gb</amdefault>.
+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.</para>
+<para>The default unit is Kbytes if it is not specified.</para>
+
+<para>If 0 is specified, Amanda will create holding disk chunks as large as
+((INT_MAX/1024)-64) Kbytes.</para>
+
+<para>Each holding disk chunk includes a 32 Kbyte header, so the minimum
+chunk size is 64 Kbytes (but that would be really silly).</para>
+
+<para>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.</para>
+ </listitem>
+ </varlistentry>
+</variablelist>
+</refsect1>
+
+<refsect1><title>DUMPTYPE SECTION</title>
+<para>The &amconf; file may define multiple sets of backup options
+and refer to them by name from the &disklist; 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.</para>
+
+<para>A set of backup options are entered in a
+<amkeyword>dumptype</amkeyword>
+section, which looks like this:</para>
+
+<programlisting>
+define dumptype "<emphasis remap='I'>name</emphasis>" {
+ <emphasis remap='I'>dumptype-option</emphasis> <emphasis remap='I'>dumptype-value</emphasis>
+ <literal>...</literal>
+}
+</programlisting>
+
+<para>The { must appear at the end of a line, and the } on its own line.</para>
+<para><emphasis remap='I'>Name</emphasis>
+is the name of this set of backup options.
+It is referenced from the &disklist; file.</para>
+
+<para>Some of the options in a
+<amkeyword>dumptype</amkeyword>
+section are the same as those in the main part of &amconf;.
+The main option value is used to set the default for all
+<amkeyword>dumptype</amkeyword>
+sections. For instance, setting
+<amkeyword>dumpcycle</amkeyword>
+to 50 in the main part of the config file causes all following
+<amkeyword>dumptype</amkeyword>
+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
+<amkeyword>dumptype</amkeyword>s
+are defined.</para>
+
+<para>The dumptype options and values are:</para>
+
+<variablelist remap='TP'>
+ <varlistentry>
+ <term><amkeyword>auth</amkeyword> <amtype>string</amtype></term>
+ <listitem>
+<para>Default:
+<amdefault>"bsd"</amdefault>.
+Type of authorization to perform between tape server and backup client hosts. See <manref name="amanda-auth" vol="7"/> for more detail.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>amandad-path</amkeyword> <amtype>string</amtype></term>
+ <listitem>
+<para>Default:
+<amdefault>"$libexec/amandad"</amdefault>.
+Specify the amandad path of the client, only use with rsh/ssh authentification.
+</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>client-username</amkeyword> <amtype>string</amtype></term>
+ <listitem>
+<para>Default:
+<amdefault>CLIENT_LOGIN</amdefault>.
+Specify the username to connect on the client, only use with rsh/ssh authentification.
+</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>client-port</amkeyword> [ <amtype>int</amtype> | <amtype>string</amtype> ]</term>
+ <listitem>
+<para>Default:
+<amdefault>"amanda"</amdefault>.
+Specifies the port to connect to on the client. It can be a service name or a numeric port number.
+</para>
+ </listitem>
+ </varlistentry>
+
+<!-- bumping parameters yanked from the global section above -->
+
+ <varlistentry>
+ <term><amkeyword>bumpsize</amkeyword> <amtype>int</amtype></term>
+ <listitem>
+<para>Default:
+<amdefault>10 Mbytes</amdefault>.
+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
+<emphasis>bumppercent</emphasis> is set to 0.
+</para>
+<para>The default unit is Kbytes if it is not specified.</para>
+<para>
+See also the options
+<amkeyword>bumppercent</amkeyword>,
+<amkeyword>bumpmult</amkeyword> and
+<amkeyword>bumpdays</amkeyword>.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><amkeyword>bumppercent</amkeyword> <amtype>int</amtype></term>
+ <listitem>
+<para>Default:
+<amdefault>0</amdefault>.