amanda.conf.5

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

\fBinparallel\fR int
.RS 4
Default:
10\. The maximum number of backups that
\fIAmanda\fR
will attempt to run in parallel\.
\fIAmanda\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\.
.RE
.PP
\fBdisplayunit\fR "k|m|g|t"
.RS 4
Default:
"k"\. The unit used to print many numbers, k=kilo, m=mega, g=giga, t=tera\.
.RE
.PP
\fBdumporder\fR string
.RS 4
Default:
\fItttTTTTTTT\fR\. The priority order of each dumper:
.sp
.RS 4
.nf
s: smallest size
S: largest size
t: smallest time
T: largest time
b: smallest bandwidth
B: largest bandwidth
.fi
.RE
.RE
.PP
\fBmaxdumps\fR int
.RS 4
Default:
1\. The maximum number of backups from a single host that
\fIAmanda\fR
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 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
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 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
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 \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\.
.sp
The global setting of this parameter can be overwritten inside of a dumptype\-definition\.
.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\.
.sp
The global setting of this parameter can be overwritten inside of a dumptype\-definition\.
.RE
.PP
\fBdiskfile\fR \fI string\fR
.RS 4
Default:
\fIdisklist\fR\. The file name for the
\fIdisklist\fR
file holding client hosts, disks and other client dumping information\.
.RE
.PP
\fBinfofile\fR \fI string\fR
.RS 4
Default:
\fI/usr/adm/amanda/curinfo\fR\. The file or directory name for the historical information database\. If
\fIAmanda\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\.
.RE
.PP
\fBlogdir\fR \fI string\fR
.RS 4
Default:
\fI/usr/adm/amanda\fR\. The directory for the
\fBamdump\fR
and
\fBlog\fR
files\.
.RE
.PP
\fBindexdir\fR \fI string\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 \fI string\fR
.RS 4
Default:
\fItapelist\fR\. The file name for the active
\fItapelist\fR
file\.
\fIAmanda\fR
maintains this file with information about the active set of tapes\.
.RE
.PP
\fBdevice_output_buffer_size\fR \fI int\fR
.RS 4
Default:
640k\. Controls the amount of memory used by
\fIAmanda\fR
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\.
.RE
.PP
\fBtapebufs\fR \fI int\fR
.RS 4
Default:
20\. 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 \fI number\fR
.RS 4
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\.
.RE
.PP
\fBautoflush\fR \fI bool\fR
.RS 4
Default:
\fIoff\fR\. Whether an amdump run will flush the dumps from holding disk to tape\.
.RE
.PP
\fBamrecover_do_fsf\fR \fI bool\fR
.RS 4
Default:
\fIon\fR\. Amrecover will call amrestore with the \-f flag for faster positioning of the tape\.
.RE
.PP
\fBamrecover_check_label\fR \fI bool\fR
.RS 4
Default:
\fIon\fR\. Amrecover will call amrestore with the \-l flag to check the label\.
.RE
.PP
\fBamrecover_changer\fR \fI string\fR
.RS 4
Default: \'\'\. Amrecover will use the changer if you use \'settape <string>\' and that string is the same as the amrecover_changer setting\.
.RE
.PP
\fBcolumnspec\fR \fI string\fR
.RS 4
Defines the width of columns
\fBamreport\fR
should use\.
\fIString\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:
.sp
.RS 4
\h'-04' 1.\h'+02'the name of the column, which may be:
.sp
.RS 4
.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
.RE
.sp
.RS 4
\h'-04' 2.\h'+02'the amount of space to display before the column (used to get whitespace between columns)\.
.sp
.RE
.sp
.RS 4
\h'-04' 3.\h'+02'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
.IP "" 4
Here is an example:
.sp
.RS 4
.nf
columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"
.fi
.RE
.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 output KBytes column is seven characters wide with one space before it\.
.RE
.PP
\fBincludefile\fR \fI string\fR
.RS 4
Default:
\fInone\fR\. The name of an
\fIAmanda\fR
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_auth\fR int
.RS 4
Default:
\fI0\fR\. Debug level of the auth module
.RE
.PP
\fBdebug_event\fR int
.RS 4
Default:
\fI0\fR\. Debug level of the event module
.RE
.PP
\fBdebug_holding\fR int
.RS 4
Default:
\fI0\fR\. Debug level of the holdingdisk module
.RE
.PP
\fBdebug_protocol\fR int
.RS 4
Default:
\fI0\fR\. Debug level of the protocol module
.RE
.PP
\fBdebug_planner\fR int
.RS 4
Default:
\fI0\fR\. Debug level of the planner process
.RE
.PP
\fBdebug_driver\fR int
.RS 4
Default:
\fI0\fR\. Debug level of the driver process
.RE
.PP
\fBdebug_dumper\fR int
.RS 4
Default:
\fI0\fR\. Debug level of the dumper process
.RE
.PP
\fBdebug_chunker\fR int
.RS 4
Default:
\fI0\fR\. Debug level of the chunker process
.RE
.PP
\fBdebug_taper\fR int
.RS 4
Default:
\fI0\fR\. Debug level of the taper process
.RE
.PP
\fBflush\-threshold\-dumped\fR int
.RS 4
Default:
\fI0\fR\.
\fIAmanda\fR
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,
\fIAmanda\fR
will not begin until the inequality
h < t \(mu d
is satisfied, where
h
is the amount of data on the holding disk,
t
is the capacity of a volume, and
d
is this parameter, expressed as a percentage\.
.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
\fIAmanda\fR
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 int
.RS 4
Default:
\fI0\fR\.
\fIAmanda\fR
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,
\fIAmanda\fR
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\.
.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
\fIAmanda\fR
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 int
.RS 4
Default:
\fI0\fR\. At the end of a run,
\fIAmanda\fR
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,
\fIAmanda\fR
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\.
.sp
The value of this parameter may not exceed that of the
\fBflush\-threshold\-scheduled\fR
parameter\.;
\fBautoflush\fR
must be set to \'yes\' if
\fBtaperflush\fR
is greater than 0\.
.RE
.PP
\fBreserved\-udp\-port\fR int,int
.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 int,int
.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 int,int
.RS 4
Default: \-\-with\-tcpportrange or
\fI1024,65535\fR\. Unreserved tcp port that will be used (bsd, bsdudp)\. Range is inclusive\.
.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:
.sp
.RS 4
.nf
holdingdisk \fIname\fR {
    \fIholdingdisk\-option\fR \fIholdingdisk\-value\fR
    \.\.\.
}
.fi
.RE
.PP
\fIName\fR
is a logical name for this holding disk\.
.PP
The options and values are:
.PP
\fBcomment\fR \fI string\fR
.RS 4
Default:
\fInone\fR\. A comment string describing this holding disk\.