-\fBarchive\fR
-configuration for infrequent full archival backups. The configuration files would be stored under directories
-\fI/usr/local/etc/amanda/normal/\fR
-and
-\fI/usr/local/etc/amanda/archive/\fR, respectively. Part of the job of an
-\fBAmanda\fR
-administrator is to create, populate and maintain these directories.
-.PP
-All log and database files generated by
-\fBAmanda\fR
-go in corresponding directories somewhere. The exact location is controlled by entries in
-\fBamanda.conf\fR. A typical location would be under
-\fI/var/adm/amanda\fR. For the above example, the files might go in
-\fI/var/adm/amanda/normal/\fR
-and
-\fI/var/adm/amanda/archive/\fR.
-.PP
-As log files are no longer needed (no longer contain relevant information),
-\fBAmanda\fR
-cycles them out in various ways, depending on the type of file.
-.PP
-Detailed information about
-\fBamdump\fR
-runs are stored in files named
-\fBamdump.\fR\fBNN\fR
-where
-\fBNN\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 named
-\fBlog.\fR\fBYYYYMMDD.NN\fR
-where
-\fBYYYYMMDD\fR
-is the datestamp of the start of the
-\fBamdump\fR
-run and
-\fBNN\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
-\fBAmanda\fR
-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 "DISKLIST FILE"
-.PP
-The
-\fBdisklist\fR
-file determines which disks will be backed up by
-\fBAmanda\fR. The file usually contains one line per disk:
-.nf
-
-\fBhostname diskname\fR [\fBdiskdevice\fR] \fBdumptype\fR [\fBspindle\fR [\fBinterface\fR] ]
-.fi
-.PP
-All pairs [
-\fBhostname diskname\fR
-] must be unique.
-.PP
-Lines starting with # are ignored, as are blank lines. The fields have the following meanings:
-.TP
-\fBhostname\fR
-The name of the host to be backed up. If
-\fBdiskdevice\fR
-refers to a PC share, this is the host
-\fBAmanda\fR
-will run the Samba
-\fBsmbclient\fR
-program on to back up the share.
-.TP
-\fBdiskname\fR
-The name of the disk (a label). In most case, you set your
-\fBdiskname\fR
-to the
-\fBdiskdevice\fR
-and you don't set the
-\fBdiskdevice.\fR
-If you want multiple entries with the same
-\fBdiskdevice\fR, you must set a different
-\fBdiskname\fR
-for each entry. It's the
-\fBdiskname\fR
-that you use on the commandline for any
-\fBAmanda\fR
-command. Look at the example/disklist file for example.
-.TP
-\fBdiskdevice\fR
-Default: same as diskname. The name of the disk device to be backed up. It may be a full device name, a device name without the
-\fI/dev/\fR
-prefix, e.g.
-\fBsd0a\fR, or a mount point such as
-\fI/usr\fR.
-.sp
-It may also refer to a PC share by starting the name with two (forward) slashes, e.g.
-\fI//some-pc/home\fR. In this case, the
-\fBprogram\fR
-option in the associated
-\fBdumptype\fR
-must be entered as
-\fBGNUTAR\fR. It is the combination of the double slash disk name and
-\fBprogram GNUTAR\fR
-in the
-\fBdumptype\fR
-that triggers the use of Samba.
-.TP
-\fBdumptype\fR
-Refers to a
-\fBdumptype\fR
-defined in the
-\fBamanda.conf\fR
-file.
-\fBDumptype\fRs specify backup related parameters, such as whether to compress the backups, whether to record backup results in
-\fI/etc/dumpdates\fR, the disk's relative priority, etc.
-.TP
-\fBspindle\fR
-Default:
-\fB-1\fR. A number used to balance backup load on a host.
-\fBAmanda\fR
-will not run multiple backups at the same time on the same spindle, unless the spindle number is -1, which means there is no spindle restriction.
-.TP
-\fBinterface\fR
-Default:
-\fBlocal\fR. The name of a network interface definition in the
-\fBamanda.conf\fR
-file, used to balance network load.
-.PP
-Instead of naming a
-\fBdumptype\fR, it is possible to define one in-line, enclosing
-\fBdumptype\fR
-options within curly braces, one per line, just like a
-\fBdumptype\fR
-definition in
-\fBamanda.conf\fR. Since pre-existing
-\fBdumptype\fRs are valid option names, this syntax may be used to customize
-\fBdumptype\fRs for particular disks.
-.PP
-A line break
-\fBmust\fR
-follow the left curly bracket.
-.PP
-For instance, if a
-\fBdumptype\fR
-named
-\fBnormal\fR
-is used for most disks, but use of the holding disk needs to be disabled for the file system that holds it, this would work instead of defining a new dumptype:
-.nf
-
-\fBhostname diskname\fR [ \fBdiskdevice\fR ] {
- normal
- holdingdisk never
-} [ \fBspindle\fR [ \fBinterface\fR ] ]
-.fi
-.SH "TAPE MANAGEMENT"
-.PP
-The
-\fBtapelist\fR
-file contains the list of tapes in active use. This file is maintained entirely by
-\fBAmanda\fR
-and should not be created or edited during normal operation. It contains lines of the form:
-.PP
-
-.sp
-.nf
-YYYYMMDD label flags
-.fi
-
-.PP
-Where
-\fBYYYYMMDD\fR
-is the date the tape was written,
-\fBlabel\fR
-is a label for the tape as written by
-\fBamlabel\fR