amanda.8

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

.RE
.PP
\fInull\fR
.RS 4
This driver throws away anything written to it and returns EOF for any reads except a special case is made for reading a label, in which case a "fake" value is returned that
\fIAmanda\fR
checks for and allows through regardless of what you have set in
\fBlabelstr\fR\. The
\fIdriver\-info\fR
field is not used and may be left blank:
.sp
.sp
.RS 4
.nf
tapedev null:
.fi
.RE
.sp
The
\fIlength\fR
value from the associated
\fBtapetype\fR
is used to limit the amount of data written\. When the limit is reached, the driver will simulate end of tape\.
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
Note
This driver should only be used for debugging and testing, and probably only with the
\fBrecord\fR
option set to
\fIno\fR\.
.RE
.PP
\fIrait\fR
.RS 4
\fIR\fRedundant
\fIA\fRrray of
\fII\fRnexpensive (?)
\fIT\fRapes\. Reads and writes tapes mounted on multiple drives by spreading the data across N\-1 drives and using the last drive for a checksum\. See docs/RAIT for more information\.
.sp
The
\fIdriver\-info\fR
field describes the devices to use\. Curly braces indicate multiple replacements in the string\. For instance:
.sp
.sp
.RS 4
.nf
tapedev rait:/dev/rmt/tps0d{4,5,6}n
.fi
.RE
.sp
would use the following devices:
.sp
\fI/dev/rmt/tps0d4n\fR
\fI/dev/rmt/tps0d5n\fR
\fI/dev/rmt/tps0d6n\fR
.RE
.PP
\fIfile\fR
.RS 4
This driver emulates a tape device with a set of files in a directory\. The
\fIdriver\-info\fR
field must be the name of an existing directory\. The driver will test for a subdirectory of that named
\fIdata\fR
and return
\fBoffline\fR
until it is present\. When present, the driver uses two files in the
\fIdata\fR
subdirectory for each tape file\. One contains the actual data\. The other contains record length information\.
.sp
The driver uses a file named
\fIstatus\fR
in the
\fBfile\fR
device directory to hold driver status information, such as tape position\. If not present, the driver will create it as though the device is rewound\.
.sp
The
\fIlength\fR
value from the associated
\fBtapetype\fR
is used to limit the amount of data written\. When the limit is reached, the driver will simulate end of tape\.
.sp
One way to use this driver with a real device such as a CD\-writer is to create a directory for the
\fBfile\fR
device and one or more other directories for the actual data\. Create a symlink named
\fIdata\fR
in the
\fBfile\fR
directory to one of the data directories\. Set the
\fBtapetype\fR
length to whatever the medium will hold\.
.sp
When
\fIAmanda\fR
fills the
\fBfile\fR
device, remove the symlink and (optionally) create a new symlink to another data area\. Use a CD writer software package to burn the image from the first data area\.
.sp
To read the CD, mount it and create the
\fIdata\fR
symlink in the
\fBfile\fR
device directory\.
.RE
.SH "AUTHORIZATION"
.PP
\fIAmanda\fR
processes on the tape server host run as the
\fBdumpuser\fR
user listed in
\fBamanda\.conf\fR\. When they connect to a backup client, they do so with an
\fIAmanda\fR\-specific protocol\. They do not, for instance, use
\fBrsh\fR
or
\fBssh\fR
directly\.
.PP
On the client side, the
\fBamandad\fR
daemon validates the connection using one of several methods, depending on how it was compiled and on options it is passed:
.PP
\.rhosts
.RS 4
Even though
\fIAmanda\fR
does not use
\fBrsh\fR, it can use
\fB\.rhosts\fR\-style authentication and a
\fB\.rhosts\fR
file\.
.RE
.PP
\.amandahosts
.RS 4
This is essentially the same as
\fB\.rhosts\fR
authentication except a different file, with almost the same format, is used\. This is the default mechanism built into
\fIAmanda\fR\.
.sp
The format of the
\fI\.amandahosts\fR
file is:
.sp
\fIhostname\fR
[
\fIusername\fR
[
\fIservice\fR
]*]
.sp
If
\fIusername\fR
is ommitted, it defaults to the user running
\fBamandad\fR, i\.e\. the user listed in the
\fBinetd\fR
or
\fBxinetd\fR
configuration file\.
.sp
The
\fIservice\fR
is a list of the service the client is authorized to execute:
\fBamdump\fR,
\fBnoop\fR,
\fBselfcheck\fR,
\fBsendsize\fR,
\fBsendbackup\fR,
\fBamindexd\fR,
\fBamidxtaped\fR\.
\fBamdump\fR
is a shortcut for "noop selfcheck sendsize sendbackup"
.RE
.PP
Kerberos
.RS 4
\fIAmanda\fR
may use the Kerberos authentication system\. Further information is in the
\fBdocs/KERBEROS\fR
file that comes with an
\fIAmanda\fR
distribution\.
.sp
For Samba access,
\fIAmanda\fR
needs a file on the Samba server (which may or may not also be the tape server) named
\fI/etc/amandapass\fR
with share names, (clear text) passwords and (optional) domain names, in that order, one per line, whitespace separated\. By default, the user used to connect to the PC is the same for all PC\'s and is compiled into
\fIAmanda\fR\. It may be changed on a host by host basis by listing it first in the password field followed by a percent sign and then the password\. For instance:
.sp
.RS 4
.nf
  //some\-pc/home normalpw
  //another\-pc/disk otheruser%otherpw
.fi
.RE
With clear text passwords, this file should obviously be tightly protected\. It only needs to be readable by the
\fIAmanda\fR\-user on the Samba server\.
.sp
You can find further information in the
\fBdocs/SAMBA\fR
file that comes with an
\fIAmanda\fR
distribution\.
.RE
.SH "HOST & DISK EXPRESSION"
.PP
All host and disk arguments to programs are special expressions\. The command applies to all disks that match your arguments\. This section describes the matcher\.
.PP
The matcher matches by word, each word is a glob expression, words are separated by the separator \'\.\' for host and \'/\' for disk\. You can anchor the expression at left with a \'^\'\. You can anchor the expression at right with a \'$\'\. The matcher is case insensitive for host but is case sensitive for disk\. A match succeeds if all words in your expression match contiguous words in the host or disk\.
.TS
tab(:);
l l
l l
l l
l l
l l
l l
l l.
T{
\.
T}:T{
word separator for a host
T}
T{
/
T}:T{
word separator for a disk
T}
T{
^
T}:T{
anchor at left
T}
T{
$
T}:T{
anchor at right
T}
T{
?
T}:T{
match exactly one character except the separator
T}
T{
*
T}:T{
match zero or more characters except the separator
T}
T{
**
T}:T{
match zero or more characters including the separator
T}
.TE
.PP
Some examples:
.TS
tab(:);
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l
l l l.
T{
EXPRESSION
T}:T{
WILL MATCH
T}:T{
WILL NOT MATCH
T}
T{
hosta
T}:T{
hosta
T}:T{
hostb
T}
T{
\ 
T}:T{
hoSTA\.dOMAIna\.ORG
T}:T{
\ 
T}
T{
\ 
T}:T{
foo\.hosta\.org
T}:T{
\ 
T}
T{
host
T}:T{
host
T}:T{
hosta
T}
T{
host?
T}:T{
hosta
T}:T{
host
T}
T{
\ 
T}:T{
hostb
T}:T{
\ 
T}
T{
ho*na
T}:T{
hoina
T}:T{
ho\.aina\.org
T}
T{
ho**na
T}:T{
hoina
T}:T{
\ 
T}
T{
\ 
T}:T{
ho\.aina\.org
T}:T{
\ 
T}
T{
^hosta
T}:T{
hosta
T}:T{
foo\.hosta\.org
T}
T{
sda*
T}:T{
/dev/sda1
T}:T{
\ 
T}
T{
\ 
T}:T{
/dev/sda12
T}:T{
\ 
T}
T{
/opt
T}:T{
opt (disk)
T}:T{
opt (host)
T}
T{
\.opt\.
T}:T{
opt (host)
T}:T{
opt (disk)
T}
T{
/
T}:T{
/
T}:T{
any other disk
T}
T{
/usr
T}:T{
/usr
T}:T{
\ 
T}
T{
\ 
T}:T{
/usr/opt
T}:T{
\ 
T}
T{
/usr$
T}:T{
/usr
T}:T{
/usr/opt
T}
.TE
.sp
.SH "DATESTAMP EXPRESSION"
.PP
A
\fIdatestamp\fR
expression is a range expression where we only match the prefix\. Leading ^ is removed\. Trailing $ forces an exact match\.
.TS
allbox tab(:);
l l
l l
l l
l l
l l
l l
l l.
T{
20001212\-14
T}:T{
match all dates beginning with 20001212, 20001213 or 20001214
T}
T{
20001212\-4
T}:T{
same as previous
T}
T{
20001212\-24
T}:T{
match all dates between 20001212 and 20001224
T}
T{
2000121
T}:T{
match all dates that start with 2000121 (20001210\-20001219)
T}
T{
2
T}:T{
match all dates that start with 2 (20000101\-29991231)
T}
T{
2000\-10
T}:T{
match all dates between 20000101\-20101231
T}
T{
200010$
T}:T{
match only 200010
T}
.TE
.PP
.SH "DUMP SPECIFICATIONS"
.PP
A dump specification selects one or more dumps\. It has the form
\fI[host][:disk][@datestamp]\fR, where each component is a pattern as described above\. If a component is missing, it is treated as a wildcard\. The characters \':\', \'@\', and \'\e\' may be escaped within any component by preceding them with a \'\e\'\.
.PP
Some examples:
.TS
tab(:);
l l
l l
l l
l l
l l
l l.
T{
DUMPSPEC
T}:T{
DESCRIPTION
T}
T{
client17
T}:T{
all dumps of client17
T}
T{
@20080615
T}:T{
All dumps on with datestamps matching 20080615
T}
T{
webserver:/var/www
T}:T{
All dumps of /var/www on host webserver
T}
T{
webserver:/var/www@200806150317
T}:T{
The dump of webserver with datestamp 200806150317
T}
T{
:/var/www
T}:T{
All dumps of /var/www on any host
T}
.TE
.sp
.SH "CONFIGURATION OVERRIDE"
.PP
Most commands allow the override of specific configuration options on the command line, using the
\-o
option\. This option has the form
\-o\fIname\fR=\fIvalue\fR\. An optional space is allowed after the
\-o\. Each configuration option should be specified in a separate command\-line option\.
.PP
For global options,
\fIname\fR
is simply the name of the option, e\.g\.,
.sp
.RS 4
.nf
amdump \-oruntapes=2
.fi
.RE
.sp
For options in a named section of the configuration,
\fIname\fR
has the form
\fISECTION\fR:\fIsection_name\fR:\fIname\fR, where
\fISECTION\fR
is one of TAPETYPE, DUMPTYPE, HOLDINGDISK, or INTERFACE, and
\fIsection_name\fR
is the name of the tapetype, dumptype, holdingdisk, or interface\. Examples:
.sp
.RS 4
.nf
amdump \-o TAPETYPE:HP\-DAT:length=2000m
amdump \-o DUMPTYPE:no\-compress:compress="server fast"
amdump \-o HOLDINGDISK:hd1:use="\-100 mb"
amdump \-o INTERFACE:local:use="2000 kbps"
.fi
.RE
.PP
Note that configuration overrides are not effective for tape changers, which supply a tapedev based on their own configuration\. In order to override
\fItapedev\fR, you must also disable any changer:
.sp
.RS 4
.nf
amdump \-otapedev=/dev/nst1 \-otpchanger=\'\'
.fi
.RE
.sp
.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
.SH "SEE ALSO"
.PP

\fBamadmin\fR(8),
\fBamanda.conf\fR(5),
\fBamanda-client.conf\fR(5),
\fBamcheck\fR(8),
\fBamcheckdb\fR(8),
\fBamcleanup\fR(8),
\fBamdd\fR(8),
\fBamdump\fR(8),
\fBamfetchdump\fR(8)
\fBamflush\fR(8),
\fBamgetconf\fR(8),
\fBamlabel\fR(8),
\fBammt\fR(8),
\fBamoverview\fR(8),
\fBamplot\fR(8),
\fBamrecover\fR(8),
\fBamreport\fR(8),
\fBamrestore\fR(8),
\fBamrmtape\fR(8),
\fBamstatus\fR(8),
\fBamtape\fR(8),
\fBamtapetype\fR(8),
\fBamtoc\fR(8),
\fBamcheckdump\fR(8),
\fBamserverconfig\fR(8),
\fBamaddclient\fR(8),
\fI\%http://wiki.zmanda.com\fR