.\" Title: amanda
.\" Author: James da Silva <jds@amanda.org>
.\" Generator: DocBook XSL Stylesheets vsnapshot_8273 <http://docbook.sf.net/>
-.\" Date: 06/01/2010
+.\" Date: 10/18/2010
.\" Manual: System Administration Commands
-.\" Source: Amanda 3.1.0
+.\" Source: Amanda 3.2.0
.\" Language: English
.\"
-.TH "AMANDA" "8" "06/01/2010" "Amanda 3\&.1\&.0" "System Administration Commands"
+.TH "AMANDA" "8" "10/18/2010" "Amanda 3\&.2\&.0" "System Administration Commands"
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.sp -1
.IP \(bu 2.3
.\}
+\fBamanda-match\fR(7),
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
\fBamanda-scripts\fR(7),
.RE
.sp
.\}
\fBamanda-taperscan\fR(7),
.RE
-.SH "CONFIGURATION"
+.SH "CONFIGURATION FILES"
.PP
There are four user\-editable files that control the behavior of Amanda\&.
.PP
normal\&. If the parameter is
\&.
(dot), the current directory is used\&. This feature is present for backward compatibility, but is not commonly used\&.
-.SH "LOG FILES"
-.PP
-All log and database files generated by Amanda go in corresponding directories somewhere\&. The exact location is controlled by entries in
-\fBamanda.conf\fR(5)\&. A typical location would be under
-/var/adm/amanda\&. For the above example, the files might go in
-/var/adm/amanda/normal/
-and
-/var/adm/amanda/archive/\&.
-.PP
-As log files are no longer needed (no longer contain relevant information), Amanda cycles them out in various ways, depending on the type of file\&.
-.PP
-Detailed information about
-\fBamdump\fR
-runs are stored in dump logs \-\- files named
-\fBamdump\&.\fR\fINN\fR
-where
-\fINN\fR
-is a sequence number, with 1 being the most recent file\&.
-\fBAmdump\fR
-rotates these files each run, keeping roughly the last
-\fBtapecycle\fR
-(see below) worth of them\&.
-.PP
-The file used by
-\fBamreport\fR
-to generate the mail summary is the trace log\&. This file constitutes the "catalog" describing the data on the tapes written in a run\&. It is named
-\fBlog\&.\fR\fIYYYYMMDDHHMMSS\&.NN\fR
-where
-\fIYYYYMMDDHHMMSS\fR
-is the datestamp of the start of the
-\fBamdump\fR
-or
-\fBamflush\fR
-run and
-\fINN\fR
-is a sequence number started at 0\&. At the end of each
-\fBamdump\fR
-run, log files for runs whose tapes have been reused are renamed into a subdirectory of the main log directory (see the
-\fBlogdir\fR
-parameter below) named
-\fBoldlog\fR\&. It is up to the Amanda administrator to remove them from this directory when desired\&.
-.PP
-Index (backup image catalogue) files older than the full dump matching the oldest backup image for a given client and disk are removed by
-\fBamdump\fR
-at the end of each run\&.
-.SH "USING SAMBA"
-.PP
-For Samba access, Amanda needs a file on the Samba server (which may or may not also be the tape server) named
-/etc/amandapass
-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 Amanda\&. 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:
-.nf
- //some\-pc/home normalpw
- //another\-pc/disk otheruser%otherpw
-.fi
-.PP
-With clear text passwords, this file should obviously be tightly protected\&. It only needs to be readable by the Amanda\-user on the Samba server\&.
-.SH "HOST & DISK EXPRESSION"
-.PP
-All host and disk arguments to programs are special expressions\&. The command applies to all DLEs that match the 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\&.
-.PP
-If the disk is a UNC ("\e\ewindows\eshare") then all \'\e\' are converted to \'/\' before the match\&. Using \'\e\' is complicated because of the extra quoting required by the shell and amanda\&. It\'s easier to use \'/\' because it require less quoting ("//windows/share")
-.PP
-dot (\&.)
-.RS 4
-word separator for a host
-.RE
-.PP
-/
-.RS 4
-word separator for a disk
-.RE
-.PP
-\e
-.RS 4
-word separator for a UNC disk
-.RE
-.PP
-^
-.RS 4
-anchor at left
-.RE
-.PP
-$
-.RS 4
-anchor at right
-.RE
-.PP
-?
-.RS 4
-match exactly one character except the separator
-.RE
-.PP
-*
-.RS 4
-match zero or more characters except the separator
-.RE
-.PP
-**
-.RS 4
-match zero or more characters including the separator
-.RE
-.PP
-[\&.\&.\&.]
-.RS 4
-match a single character, namely any of the characters enclosed by the brackets\&.
-.RE
-.PP
-[!\&.\&.\&.]
-.RS 4
-match a single character, namely any characters that is not enclosed by the brackets\&.
-.RE
-.PP
-The shell interpret some of these characters, they must be escaped by a backslash \'\e\' and/or the expression must be enclosed in simple or double quote\&.
-.PP
-Some examples:
-.PP
-hosta
-.RS 4
-Will match
-hosta,
-foo\&.hosta\&.org, and
-hoSTA\&.dOMAIna\&.ORG
-but not
-hostb\&.
-.RE
-.PP
-host
-.RS 4
-Will match
-host
-but not
-hosta\&.
-.RE
-.PP
-host?
-.RS 4
-Will match
-hosta
-and
-hostb, but not
-host\&.
-.RE
-.PP
-ho*na
-.RS 4
-Will match
-hoina
-but not
-ho\&.aina\&.org\&.
-.RE
-.PP
-ho**na
-.RS 4
-Will match
-hoina
-and
-ho\&.aina\&.org\&.
-.RE
-.PP
-^hosta
-.RS 4
-Will match
-hosta
-but not
-foo\&.hosta\&.org\&.
-.RE
-.PP
-sda*
-.RS 4
-Will match
-/dev/sda1
-and
-/dev/sda12\&.
-.RE
-.PP
-/opt
-.RS 4
-Will match the disk
-opt
-but not the host
-opt\&.
-.RE
-.PP
-(note dots:) \&.opt\&.
-.RS 4
-Will match the host
-opt
-but not the disk
-opt\&.
-.RE
-.PP
-/
-.RS 4
-Will match the disk
-/
-but no other disk\&.
-.RE
-.PP
-/usr
-.RS 4
-Will match the disks
-/usr
-and
-/usr/local\&.
-.RE
-.PP
-/usr$
-.RS 4
-Will match the disks
-/usr
-but not
-/usr/local\&.
-.RE
-.PP
-share
-.RS 4
-Will match the disks
-\e\ewindows1\eshare
-and
-\e\ewindows2\eshare\&.
-.RE
-.PP
-share*
-.RS 4
-Will match the disks
-\e\ewindows\eshare1
-and
-\e\ewindows\eshare2\&.
-.RE
-.PP
-//windows/share
-.RS 4
-Will match the disk
-\e\ewindows\eshare\&.
-.RE
-.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\&.
-.PP
-20001212\-14
-.RS 4
-match all dates beginning with 20001212, 20001213 or 20001214
-.RE
-.PP
-20001212\-4
-.RS 4
-same as previous
-.RE
-.PP
-20001212\-24
-.RS 4
-match all dates between 20001212 and 20001224
-.RE
-.PP
-2000121
-.RS 4
-match all dates that start with 2000121 (20001210\-20001219)
-.RE
-.PP
-2
-.RS 4
-match all dates that start with 2 (20000101\-29991231)
-.RE
-.PP
-2000\-10
-.RS 4
-match all dates between 20000101\-20101231
-.RE
-.PP
-200010$
-.RS 4
-match only 200010
-.RE
-.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:
-.PP
-client17
-.RS 4
-all dumps of client17
-.RE
-.PP
-@20080615
-.RS 4
-All dumps on with datestamps matching 20080615
-.RE
-.PP
-webserver:/var/www
-.RS 4
-All dumps of /var/www on host webserver
-.RE
-.PP
-webserver:/var/www@200806150317
-.RS 4
-The dump of webserver with datestamp 200806150317
-.RE
-.PP
-:/var/www
-.RS 4
-All dumps of /var/www on any host
-.RE
-.SH "CONFIGURATION OVERRIDE"
+.SS "Configuration Override"
.PP
Most commands allow the override of specific configuration options on the command line, using the
\-o
projects / debian / amanda / blobdiff