+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\&.
+.PP
+The dumptype options and values are:
+.PP
+\fBauth\fR \fIstring\fR
+.RS 4
+Default:
+\fI"bsd"\fR\&. Type of authorization to perform between tape server and backup client hosts\&. See
+\fBamanda-auth\fR(7)
+for more detail\&.
+.RE
+.PP
+\fBamandad\-path\fR \fIstring\fR
+.RS 4
+Default:
+\fI"$libexec/amandad"\fR\&. Specify the amandad path of the client, only use with rsh/ssh authentification\&.
+.RE
+.PP
+\fBclient\-username\fR \fIstring\fR
+.RS 4
+Default:
+\fICLIENT_LOGIN\fR\&. Specify the username to connect on the client, only use with rsh/ssh authentification\&.
+.RE
+.PP
+\fBclient\-port\fR [ \fIint\fR | \fIstring\fR ]
+.RS 4
+Default:
+\fI"amanda"\fR\&. Specifies the port to connect to on the client\&. It can be a service name or a numeric port number\&.
+.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
+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
+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\&.
+.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\&.
+.RE
+.PP
+\fBcomment\fR \fIstring\fR
+.RS 4
+Default: not set\&. A comment string describing this set of backup options\&.
+.RE
+.PP
+\fBcomprate\fR \fIfloat\fR [, \fIfloat\fR ]
+.RS 4
+Default:
+\fI0\&.50, 0\&.50\fR\&. The expected full and incremental compression factor for dumps\&. It is only used if Amanda 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\&.
+.RE
+.PP
+\fBcompress\fR [ \fBnone\fR | \fBclient\fR | \fBserver\fR ] [ \fBbest\fR | \fBfast\fR | \fBcustom\fR ]
+.RS 4
+Default:
+\fBclient fast\fR\&. If Amanda 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\&.
+.sp
+For either type of compression, Amanda also allows the selection of three 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\&. Or to specify
+\fBcustom\fR
+to use your own compression method\&. (See dumptype custom\-compress in example/amanda\&.conf for reference)
+.sp
+So the
+\fBcompress\fR
+options line may be one of:
+.PP
+compress none
+.RS 4
+.RE
+.PP
+compress client fast
+.RS 4
+.RE
+.PP
+compress client best
+.RS 4
+.RE
+.PP
+compress client custom
+.RS 4
+Specify
+\fBclient\-custom\-compress\fR
+"PROG"
+.sp
+PROG must not contain white space and it must accept \-d for uncompress\&.
+.RE
+.PP
+compress server fast
+.RS 4
+.RE
+.PP
+compress server best
+.RS 4
+.RE
+.PP
+compress server custom
+.RS 4
+Specify
+\fBserver\-custom\-compress\fR
+"PROG"
+.sp
+PROG must not contain white space and it must accept \-d for uncompress\&.
+.RE
+.sp
+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), Amanda (software) compression should be disabled\&.
+.RE
+.PP
+\fBclient\-custom\-compress\fR \fIstring\fR
+.RS 4
+Default: none\&. The program to use to perform compression/decompression on the client; used with "compress client custom"\&. Must not contain whitespace\&. Must accept \-d to uncompress\&.
+.RE
+.PP
+\fBserver\-custom\-compress\fR \fIstring\fR
+.RS 4
+Default: none\&. The program to use to perform compression/decompression on the server; used with "compress server custom"\&. Must not contain whitespace\&. Must accept \-d to uncompress\&.
+.RE
+.PP
+\fBdumpcycle\fR \fIint\fR
+.RS 4
+Default:
+\fI10 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 of ten\&. Setting this to zero tries to do a full backup each run\&.
+.RE
+.PP
+\fBencrypt\fR [ \fBnone\fR | \fBclient\fR | \fBserver\fR ]
+.RS 4
+Default: not set\&. To encrypt 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\&.
+.sp
+So the
+\fBencrypt\fR
+options line may be one of:
+.PP
+encrypt none
+.RS 4
+.RE
+.PP
+encrypt client
+.RS 4
+Specify client\-encrypt "PROG"
+.sp
+PROG must not contain white space\&.
+.sp
+Specify client\-decrypt\-option "decryption\-parameter" Default: "\-d"
+.sp
+decryption\-parameter must not contain white space\&.
+.sp
+(See dumptype client\-encrypt\-nocomp in example/amanda\&.conf for reference)
+.RE
+.PP
+encrypt server
+.RS 4
+Specify server\-encrypt "PROG"
+.sp
+PROG must not contain white space\&.
+.sp
+Specify server\-decrypt\-option "decryption\-parameter" Default: "\-d"
+.sp
+decryption\-parameter must not contain white space\&.
+.sp
+(See dumptype server\-encrypt\-fast in example/amanda\&.conf for reference)
+.RE
+.sp
+Note that current logic assumes compression then encryption during backup(thus decrypt then uncompress during restore)\&. So specifying client\-encryption AND server\-compression is not supported\&.
+\fIamcrypt\fR
+which is a wrapper of
+\fIaespipe\fR
+is provided as a reference symmetric encryption program\&.
+.RE
+.PP
+\fBclient\-encrypt\fR \fIstring\fR
+.RS 4
+Default: none\&. The program to use to perform encryption/decryption on the client; used with "encrypt client"\&. Must not contain whitespace\&.
+.RE
+.PP
+\fBclient\-decrypt\-option\fR \fIstring\fR
+.RS 4
+Default: \-d\&. The option that can be passed to client\-encrypt to make it decrypt instead\&. Must not contain whitespace\&.
+.RE
+.PP
+\fBserver\-encrypt\fR \fIstring\fR
+.RS 4
+Default: none\&. The program to use to perform encryption/decryption on the server; used with "encrypt server"\&. Must not contain whitespace\&.
+.RE
+.PP
+\fBserver\-decrypt\-option\fR \fIstring\fR
+.RS 4
+Default: \-d\&. The option that can be passed to server\-encrypt to make it decrypt instead\&. Must not contain whitespace\&.
+.RE
+.PP
+\fBestimate\fR [ \fBclient\fR | \fBcalcsize\fR | \fBserver\fR ]+
+.RS 4
+Default:
+\fBclient\fR\&. Determine the way Amanda estimates the size of each DLE before beginning a backup\&. This is a list of acceptable estimate methods, and Amanda applies the first method supported by the application\&. The methods are:
+.PP
+client
+.RS 4
+Use the same program as the dumping program\&. This is the most accurate method to do estimates, but it can take a long time\&.
+.RE
+.PP
+calcsize
+.RS 4
+Use a faster program to do estimates, but the result is less accurate\&.
+.RE
+.PP
+server
+.RS 4
+Use only statistics from the previous few runs to give an estimate\&. This very quick, but the result is not accurate if your disk usage changes from day to day\&. If this method is specified, but the server does not have enough data to make an estimate, then the option is internally moved to the end of the list, thereby preferring \'client\' or \'calcsize\' in this case\&.
+.RE
+.RE
+.PP
+\fBexclude\fR [ \fBlist\fR | \fBfile\fR ][[\fBoptional\fR][\fBappend\fR][ \fIstring\fR ]+]
+.RS 4
+Default:
+\fBfile\fR\&. Exclude is the opposite of
+\fBinclude\fR
+and specifies files that will be excluded from the backup\&. The format of the exclude expressions depends on the application, and some applications do not support excluding files at all\&.
+.sp
+There are two exclude parameters,
+\fBexclude\fR
+\fBfile\fR
+and
+\fBexclude\fR
+\fBlist\&.\fR
+With
+\fBexclude\fR
+\fBfile\fR, the
+\fIstring\fR
+is an exclude expression\&. With
+\fBexclude\fR
+\fBlist\fR
+, the
+\fIstring\fR
+is a file name on the client containing
+\fBGNU\-tar\fR
+exclude expressions\&. The path to the specified exclude list file, if present (see description of \'optional\' below), must be readable by the Amanda user\&.
+.sp
+All exclude expressions are concatenated in one file and passed to the application as an
+\fB\-\-exclude\-from\fR
+argument\&.
+.sp
+For
+\fBGNU\-tar\fR, exclude expressions must always be specified as relative to the top\-level directory of the DLE, and must start with "\&./"\&. See the manpages for individual applications for more information on supported exclude expressions\&.
+.sp
+With the
+\fBappend\fR
+keyword, the
+\fIstring\fR
+is appended to the current list, without it, the
+\fIstring\fR
+overwrites the list\&.
+.sp
+If
+\fBoptional\fR
+is specified for
+\fBexclude\fR
+\fBlist\fR, then amcheck will not complain if the file doesn\'t exist or is not readable\&.
+.sp
+For
+\fBexclude\fR
+\fBlist\fR, if the file name is relative, the disk name being backed up is prepended\&. So if this is entered:
+.nf
+ exclude list "\&.amanda\&.excludes"
+.fi
+the actual file used would be
+/var/\&.amanda\&.excludes
+for a backup of
+/var,
+/usr/local/\&.amanda\&.excludes
+for a backup of
+/usr/local, and so on\&.
+.RE
+.PP
+\fBholdingdisk\fR [ \fBnever\fR | \fBauto\fR | \fBrequired\fR ]
+.RS 4
+Default:
+\fBauto\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 Amanda is backing up, that file system should refer to a dumptype with
+\fBholdingdisk\fR
+set to
+\fInever\fR
+to avoid backing up the holding disk into itself\&.
+.PP
+\fBnever\fR|no|false|off
+.RS 4
+Never use a holdingdisk, the dump will always go directly to tape\&. There will be no dump if you have a tape error\&.
+.RE
+.PP
+\fBauto\fR|yes|true|on
+.RS 4
+Use the holding disk, unless there is a problem with the holding disk, the dump won\'t fit there or the medium doesn\'t require spooling (e\&.g\&., VFS device)
+.RE
+.PP
+\fBrequired\fR
+.RS 4
+Always dump to holdingdisk, never directly to tape\&. There will be no dump if it doesn\'t fit on holdingdisk
+.RE
+.RE
+.PP
+\fBignore\fR \fIboolean\fR
+.RS 4
+Default:
+\fBno\fR\&. Whether disks associated with this backup type should be backed up or not\&. This option is useful when the
+\fIdisklist\fR
+file is shared among several configurations, some of which should not back up all the listed file systems\&.
+.RE
+.PP
+\fBinclude\fR [ \fBlist\fR | \fBfile\fR ][[\fBoptional\fR][\fBappend\fR][ \fIstring\fR ]+]
+.RS 4
+Default:
+\fBfile\fR
+"\&."\&. There are two include lists,
+\fBinclude file\fR
+and
+\fBinclude list\&.\fR
+With
+\fBinclude file\fR
+, the
+\fIstring\fR
+is a glob expression\&. With
+\fBinclude list\fR
+, the
+\fIstring\fR
+is a file name on the client containing glob expressions\&.
+.sp
+All include expressions are expanded by Amanda, 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 "/"\&.
+.sp
+Include expressions must always be specified as relative to the head directory of the DLE\&.
+.if n \{\
+.sp
+.\}
+.RS 4
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.ps +1
+\fBNote\fR
+.ps -1
+.br
+For globbing to work at all, even the limited single level, the top level directory of the DLE must be readable by the Amanda user\&.
+.sp .5v
+.RE
+With the
+\fBappend\fR
+keyword, the
+\fIstring\fR
+is appended to the current list, without it, the
+\fIstring\fR
+overwrites the list\&.
+.sp
+If
+\fBoptional\fR
+is specified for
+\fBinclude list\fR, then amcheck will not complain if the file doesn\'t exist or is not readable\&.
+.sp
+For
+\fBinclude list\fR, If the file name is relative, the disk name being backed up is prepended\&.
+.RE
+.PP
+\fBindex\fR \fIboolean\fR
+.RS 4
+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\&.
+.RE
+.PP
+\fBkencrypt\fR \fIboolean\fR
+.RS 4
+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\&.
+.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 main section parameter
+\fBinparallel\fR\&.
+.RE
+.PP
+\fBmaxpromoteday\fR \fIint\fR
+.RS 4
+Default:
+\fI10000\fR\&. 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\&.
+.RE
+.PP
+\fBpriority\fR [ \fBlow\fR | \fBmedium\fR | \fBhigh\fR ]
+.RS 4
+Default:
+\fBmedium\fR\&. When there is no tape to write to, Amanda 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\&.
+.RE
+.PP
+\fBprogram\fR [ \fB"DUMP"\fR | \fB"GNUTAR"\fR | \fB"APPLICATION"\fR ]
+.RS 4
+Default:
+\fI"DUMP"\fR\&. The type of backup to perform\&. Valid values are:
+.PP
+\fB"DUMP"\fR
+.RS 4
+The native operating system backup program\&.
+.RE
+.PP
+\fB"GNUTAR"\fR
+.RS 4
+To use GNU\-tar or to do PC backups using Samba\&.
+.RE
+.PP
+\fB"APPLICATION"\fR
+.RS 4
+To use an application, see the
+\fIapplication\fR
+option\&.
+.RE
+.RE
+.PP
+\fBapplication\fR \fIstring\fR
+.RS 4
+No default\&. Must be the name of an application if
+\fIprogram\fR
+is set to
+\fIAPPLICATION\fR\&. See APPLICATION SECTION below\&.
+.RE
+.PP
+\fBscript\fR \fIstring\fR
+.RS 4
+No default\&. Must be the name of a script\&. You can have many script\&. See SCRIPT SECTION below\&.
+.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