amanda.conf.5

开源备份软件源码 AMANDA, the Advanced Maryland Automatic Network Disk Archiver, is a backup system that a

.RE
.PP
\fBdirectory\fR \fI disk\fR
.RS 4
Default:
\fI/dumps/amanda\fR\. The path to this holding area\.
.RE
.PP
\fBuse\fR \fI int\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,
\fIAmanda\fR
will use all available space minus that value\.
.RE
.PP
\fBchunksize\fR \fI int\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
If 0 is specified,
\fIAmanda\fR
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
\fIAmanda\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\.
.RE
.SH "DUMPTYPE SECTION"
.PP
The
\fIamanda\.conf\fR
file may define multiple sets of backup options and refer to them by name from the
\fIdisklist\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:
.sp
.RS 4
.nf
define dumptype \fIname\fR {
    \fIdumptype\-option\fR \fIdumptype\-value\fR
    \.\.\.
}
.fi
.RE
.PP
\fIName\fR
is the name of this set of backup options\. It is referenced from the
\fIdisklist\fR
file\.
.PP
Some of the options in a
\fBdumptype\fR
section are the same as those in the main part of
\fIamanda\.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:
.PP
\fBauth\fR \fI string\fR
.RS 4
Default:
\fIbsd\fR\. Type of authorization to perform between tape server and backup client hosts\.
.sp
\fBbsd\fR, bsd authorization with udp initial connection and one tcp connection by data stream\.
.sp
\fBbsdtcp\fR, bsd authorization but use only one tcp connection\.
.sp
\fBbsdudp\fR, like bsd, but will use only one tcp connection for all data stream\.
.sp
\fBkrb4\fR
to use Kerberos\-IV authorization\.
.sp
\fBkrb5\fR
to use Kerberos\-V authorization\.
.sp
\fBlocal\fR, if the client is the server, it doesn\'t require authencation setup\.
.sp
\fBrsh\fR
to use rsh authorization\.
.sp
\fBssh\fR
to use OpenSSH authorization\.
.RE
.PP
\fBamandad_path\fR \fI string\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 \fI string\fR
.RS 4
Default:
\fICLIENT_LOGIN\fR\. Specify the username to connect on the client, only use with rsh/ssh authentification\.
.RE
.PP
\fBbumpsize\fR int
.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
\fIAmanda\fR
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
See also the options
\fBbumppercent\fR,
\fBbumpmult\fR
and
\fBbumpdays\fR\.
.RE
.PP
\fBbumppercent\fR int
.RS 4
Default:
\fI0 percent\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
\fIAmanda\fR
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 \fI float\fR
.RS 4
Default:
1\.5\. The bump size multiplier\.
\fIAmanda\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\.
.RE
.PP
\fBbumpdays\fR \fI int\fR
.RS 4
Default:
\fI2 days\fR\. To insure redundancy in the dumps,
\fIAmanda\fR
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 \fI string\fR
.RS 4
Default:
\fInone\fR\. A comment string describing this set of backup options\.
.RE
.PP
\fBcomprate\fR \fIfloat\fR [, \fIfloat\fR ]
.RS 4
Default:
0\.50,
0\.50\. The expected full and incremental compression factor for dumps\. It is only used if
\fIAmanda\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\.
.RE
.PP
\fBcompress [client|server]\fR \fI string\fR
.RS 4
Default:
\fIclient fast\fR\. If
\fIAmanda\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\.
.sp
For either type of compression,
\fIAmanda\fR
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
\fIclient_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
\fIserver_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),
\fIAmanda\fR
(software) compression should be disabled\.
.RE
.PP
\fBdumpcycle\fR \fI int\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 [none|client|server]\fR
.RS 4
Default:
\fInone\fR\. 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 server\-encrypt\-fast 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 client\-encrypt\-nocomp 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
\fBestimate\fR \fIclient|calcsize|server\fR
.RS 4
Default:
\fIclient\fR\. Determine the way
\fIAmanda\fR
does it\'s estimate\.
.PP
client
.RS 4
Use the same program as the dumping program, this is the most accurate way 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 run to give an estimate, it takes only a few seconds but the result is not accurate if your disk usage changes from day to day\.
.RE
.RE
.PP
\fBexclude\fR [ list|file ][[optional][ append ][ \fIstring\fR ]+]
.RS 4
Default:
\fIfile\fR\. There are two exclude lists,
\fBexclude file\fR
and
\fBexclude list\.\fR
With
\fBexclude file\fR
, the
\fIstring\fR
is a
\fBGNU\-tar\fR
exclude expression\. With
\fBexclude list\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
\fIAmanda\fR
user\.
.sp
All exclude expressions are concatenated in one file and passed to
\fBGNU\-tar\fR
as an
\fB\-\-exclude\-from\fR
argument\.
.sp
Exclude expressions must always be specified as relative to the head directory of the DLE\.
.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 list\fR, then amcheck will not complain if the file doesn\'t exist or is not readable\.
.sp
For
\fBexclude list\fR, if the file name is relative, the disk name being backed up is prepended\. So if this is entered:
.sp
.RS 4
.nf
    exclude list "\.amanda\.excludes"
.fi
.RE
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\.
.RE
.PP
\fBholdingdisk\fR [ never|auto|required ]
.RS 4
Default:
\fIauto\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
\fIAmanda\fR
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 \fI boolean\fR
.RS 4
Default:
\fIno\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 [ list|file ][[optional][ append ][ \fIstring\fR ]+]
.RS 4
Default:
\fIfile\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
\fIAmanda\fR, concatenated in one file and passed to
\fBGNU\-tar\fR
as a
\fB\-\-files\-from\fR