amanda.conf.5

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

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\.
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
Note
For globbing to work at all, even the limited single level, the top level directory of the DLE must be readable by the
\fIAmanda\fR
user\.

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 \fI boolean\fR
.RS 4
Default:
\fIno\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 \fI boolean\fR
.RS 4
Default:
\fIno\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 \fI int\fR
.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 main section parameter
\fBinparallel\fR\.
.RE
.PP
\fBmaxpromoteday\fR \fI int\fR
.RS 4
Default:
10000\. 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 \fI string\fR
.RS 4
Default:
\fImedium\fR\. When there is no tape to write to,
\fIAmanda\fR
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 \fI string\fR
.RS 4
Default:
\fIDUMP\fR\. The type of backup to perform\. Valid values are
\fBDUMP\fR
for the native operating system backup program, and
\fBGNUTAR\fR
to use
\fBGNU\-tar\fR
or to do PC backups using Samba\.
.RE
.PP
\fBrecord\fR \fI boolean\fR
.RS 4
Default:
\fIyes\fR\. Whether to ask the backup program to update its database (e\.g\.
\fI/etc/dumpdates\fR
for DUMP or
\fI/usr/local/var/amanda/gnutar\-lists\fR
for GNUTAR) of time stamps\. This is normally enabled for daily backups and turned off for periodic archival runs\.
.RE
.PP
\fBskip\-full\fR \fI boolean\fR
.RS 4
Default:
\fIno\fR\. If
\fItrue\fR
and
\fBplanner\fR
has scheduled a full backup, these disks will be skipped, and full backups should be run off\-line on these days\. It was reported that
\fIAmanda\fR
only schedules level 1 incrementals in this configuration; this is probably a bug\.
.RE
.PP
\fBskip\-incr\fR \fI boolean\fR
.RS 4
Default:
\fIno\fR\. If
\fItrue\fR
and
\fBplanner\fR
has scheduled an incremental backup, these disks will be skipped\.
.RE
.PP
\fBstarttime\fR \fI int\fR
.RS 4
Default:
\fInone\fR\. Backups will not start until after this time of day\. The value should be hh*100+mm, e\.g\. 6:30PM (18:30) would be entered as
1830\.
.RE
.PP
\fBstrategy\fR \fI string\fR
.RS 4
Default:
\fIstandard\fR\. Strategy to use when planning what level of backup to run next\. Values are:
.PP
\fBstandard\fR
.RS 4
The standard
\fIAmanda\fR
schedule\.
.RE
.PP
\fBnofull\fR
.RS 4
Never do full backups, only level 1 incrementals\.
.RE
.PP
\fBnoinc\fR
.RS 4
Never do incremental backups, only full dumps\.
.RE
.PP
\fBskip\fR
.RS 4
Never do backups (useful when sharing the
\fIdisklist\fR
file)\.
.RE
.PP
\fBincronly\fR
.RS 4
Only do incremental dumps\.
\fBamadmin force\fR
should be used to tell
\fIAmanda\fR
that a full dump has been performed off\-line, so that it resets to level 1\.
.RE
.RE
.PP
\fBtape_splitsize\fR \fI int\fR
.RS 4
Default:
\fInone\fR\. Split dump file on tape into pieces of a specified size\. This allows dumps to be spread across multiple tapes, and can potentially make more efficient use of tape space\. Note that if this value is too large (more than half the size of the average dump being split), substantial tape space can be wasted\. If too small, large dumps will be split into innumerable tiny dumpfiles, adding to restoration complexity\. A good rule of thumb, usually, is 1/10 of the size of your tape\.
.RE
.PP
\fBsplit_diskbuffer\fR \fI string\fR
.RS 4
Default:
\fInone\fR\. When dumping a split dump in PORT\-WRITE mode (usually meaning "no holding disk"), buffer the split chunks to a file in the directory specified by this option\.
.RE
.PP
\fBfallback_splitsize\fR \fI int\fR
.RS 4
Default:
\fI10M\fR\. When dumping a split dump in PORT\-WRITE mode, if no split_diskbuffer is specified (or if we somehow fail to use our split_diskbuffer), we must buffer split chunks in memory\. This specifies the maximum size split chunks can be in this scenario, and thus the maximum amount of memory consumed for in\-memory splitting\. The size of this buffer can be changed from its (very conservative) default to a value reflecting the amount of memory that each taper process on the dump server may reasonably consume\.
.RE
.PP
The following
\fBdumptype\fR
entries are predefined by
\fIAmanda\fR:
.sp
.RS 4
.nf
define dumptype no\-compress {
    compress none
}
define dumptype compress\-fast {
    compress client fast
}
define dumptype compress\-best {
    compress client best
}
define dumptype srvcompress {
    compress server fast
}
define dumptype bsd\-auth {
    auth bsd
}
define dumptype krb4\-auth {
    auth krb4
}
define dumptype no\-record {
    record no
}
define dumptype no\-hold {
    holdingdisk no
}
define dumptype no\-full {
    skip\-full yes
} 
.fi
.RE
.PP
In addition to options in a
\fBdumptype\fR
section, one or more other
\fBdumptype\fR
names may be entered, which make this
\fBdumptype\fR
inherit options from other previously defined
\fBdumptype\fRs\. For instance, two sections might be the same except for the
\fBrecord\fR
option:
.sp
.RS 4
.nf
define dumptype normal {
    comment "Normal backup, no compression, do indexing"
    no\-compress
    index yes
    maxdumps 2
}
define dumptype testing {
    comment "Test backup, no compression, do indexing, no recording"
    normal
    record no
}
.fi
.RE
.PP
\fIAmanda\fR
provides a
\fBdumptype\fR
named
\fIglobal\fR
in the sample
\fBamanda\.conf\fR
file that all
\fBdumptype\fRs should reference\. This provides an easy place to make changes that will affect every
\fBdumptype\fR\.
.SH "TAPETYPE SECTION"
.PP
The
\fBamanda\.conf\fR
file may define multiple types of tape media and devices\. The information is entered in a
\fBtapetype\fR
section, which looks like this in the config file:
.sp
.RS 4
.nf
define tapetype \fIname\fR {
    \fItapetype\-option\fR \fItapetype\-value\fR
    \.\.\.
}
.fi
.RE
.PP
\fIName\fR
is the name of this type of tape medium/device\. It is referenced from the
\fBtapetype\fR
option in the main part of the config file\.
.PP
The tapetype options and values are:
.PP
\fBcomment\fR \fI string\fR
.RS 4
Default:
\fInone\fR\. A comment string describing this set of tape information\.
.RE
.PP
\fBfilemark\fR \fI int\fR
.RS 4
Default:
\fI1 kbytes\fR\. How large a file mark (tape mark) is, measured in kbytes\. If the size is only known in some linear measurement (e\.g\. inches), convert it to kbytes using the device density\.
.RE
.PP
\fBlength\fR \fI int\fR
.RS 4
Default:
\fI2000 kbytes\fR\. How much data will fit on a tape\.
.sp
Note that this value is only used by
\fIAmanda\fR
to schedule which backups will be run\. Once the backups start,
\fIAmanda\fR
will continue to write to a tape until it gets an error, regardless of what value is entered for
\fBlength\fR
(but see the section OUTPUT DRIVERS in the
\fBamanda\fR(8)
manpage for exceptions)\.
.RE
.PP
\fBblocksize\fR \fI int\fR
.RS 4
Default:
\fI32 kbytes\fR\. How much data will be written in each tape record expressed in KiloBytes\. The tape record size (= blocksize) can not be reduced below the default 32 KBytes\. The parameter blocksize can only be raised if
\fIAmanda\fR
was compiled with the configure option \-\-with\-maxtapeblocksize=N set with "N" greater than 32 during
\fBconfigure\fR\.
.RE
.PP
\fBreadblocksize\fR \fI int\fR
.RS 4
Default: (\fIfrom configure \-\-with\-maxtapeblocksize\fR)\. How much data will be read in each tape record expressed in KiloBytes\. Some hardware require a value not too large, and some require it to be equal to the blocksize\. It is useful if you configured amanda with a big \-\-with\-maxtapeblocksize and your hardware don\'t work with a value that big\.
.RE
.PP
\fBfile\-pad\fR \fI boolean\fR
.RS 4
Default:
\fItrue\fR\. If true, every record, including the last one in the file, will have the same length\. This matches the way
\fIAmanda\fR
wrote tapes prior to the availability of this parameter\. It may also be useful on devices that only support a fixed blocksize\.
.sp
Note that the last record on the tape probably includes trailing null byte padding, which will be passed back to
\fBgzip\fR,
\fBcompress\fR
or the restore program\. Most programs just ignore this (although possibly with a warning)\.
.sp
If this parameter is false, the last record in a file may be shorter than the block size\. The file will contain the same amount of data the dump program generated, without trailing null byte padding\. When read, the same amount of data that was written will be returned\.
.RE
.PP
\fBspeed\fR \fI int\fR
.RS 4
Default:
\fI200 bps\fR\. How fast the drive will accept data, in bytes per second\. This parameter is NOT currently used by
\fIAmanda\fR\.
.RE
.PP
\fBlbl\-templ\fR \fI string\fR
.RS 4
A PostScript template file used by
\fBamreport\fR
to generate labels\. Several sample files are provided with the
\fIAmanda\fR
sources in the
\fIexample\fR
directory\. See the
\fBamreport\fR(8)
man page for more information\.
.RE
.PP
In addition to options, another
\fBtapetype\fR
name may be entered, which makes this
\fBtapetype\fR
inherit options from another
\fBtapetype\fR\. For instance, the only difference between a DLT4000 tape drive using Compact\-III tapes and one using Compact\-IV tapes is the length of the tape\. So they could be entered as:
.sp
.RS 4
.nf
define tapetype DLT4000\-III {
    comment "DLT4000 tape drives with Compact\-III tapes"
    length 12500 mbytes         # 10 Gig tapes with some compression
    filemark 2000 kbytes
    speed 1536 kps
}
define tapetype DLT4000\-IV {
    DLT4000\-III
    comment "DLT4000 tape drives with Compact\-IV tapes"
    length 25000 mbytes         # 20 Gig tapes with some compression
}
.fi
.RE
.sp
.SH "INTERFACE SECTION"
.PP
The
\fBamanda\.conf\fR
file may define multiple types of network interfaces\. The information is entered in an
\fBinterface\fR
section, which looks like this:
.sp
.RS 4
.nf
define interface \fIname\fR {
    \fIinterface\-option\fR \fIinterface\-value\fR
    \.\.\.
}
.fi
.RE
.PP
\fIname\fR
is the name of this type of network interface\. It is referenced from the
\fIdisklist\fR
file\.
.PP
Note that these sections define network interface characteristics, not the actual interface that will be used\. Nor do they impose limits on the bandwidth that will actually be taken up by
\fIAmanda\fR\.
\fIAmanda\fR
computes the estimated bandwidth each file system backup will take based on the estimated size and time, then compares that plus any other running backups with the limit as another of the criteria when deciding whether to start the backup\. Once a backup starts,
\fIAmanda\fR
will use as much of the network as it can leaving throttling up to the operating system and network hardware\.
.PP
The interface options and values are:
.PP
\fBcomment\fR \fI string\fR
.RS 4
Default:
\fInone\fR\. A comment string describing this set of network information\.
.RE
.PP
\fBuse\fR \fI int\fR
.RS 4
Default:
\fI8000 Kbps\fR\. The speed of the interface in Kbytes per second\.
.RE
.PP
In addition to options, another
\fBinterface\fR
name may be entered, which makes this
\fBinterface\fR
inherit options from another
\fBinterface\fR\. At the moment, this is of little use\.
.SH "AUTHOR"
.PP
James da Silva,
<jds@amanda\.org>: Original text
.PP
Stefan G\. Weichinger,
<sgw@amanda\.org>, maintainer of the
\fIAmanda\fR\-documentation: XML\-conversion, major update, splitting
.SH "SEE ALSO"
.PP

\fBamanda\fR(8),
\fBamanda-client.conf\fR(5),
\fBamcrypt\fR(8),
\fBaespipe\fR(1),
\fI\%http://wiki.zmanda.com\fR
.PP
An updated version of this man page may be available at http://wiki\.zmanda\.com/index\.php/Amanda\.conf\.