-The supported drivers are:
-
-.TP
-\fBtape\fR
-This is the default driver\&. The \fBdriver\-info\fR is the tape device name\&. Entering
-.nf
-tapedev /dev/rmt/0mn
-.fi
- is really a short hand for
-.nf
-tapedev tape:/dev/rmt/0mn
-.fi
-\&.
-
-.TP
-\fBnull\fR
-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 \fBAMANDA\fR checks for and allows through regardless of what you have set in \fBlabelstr\fR\&. The \fBdriver\-info\fR field is not used and may be left blank:
-
-
-.nf
-tapedev null:
-.fi
-
-
-The \fBlength\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\&.
-
-.RS
-.Sh "Note"
-This driver should only be used for debugging and testing,
-and probably only with the
-\fBrecord\fR
-option set to
-\fBno\fR\&.
-.RE
-
-.TP
-\fBrait\fR
-\fBR\fRedundant \fBA\fRrray of \fBI\fRnexpensive (?) \fBT\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\&.
-
-The \fBdriver\-info\fR field describes the devices to use\&. Curly braces indicate multiple replacements in the string\&. For instance:
-
-
-.nf
-tapedev rait:/dev/rmt/tps0d{4,5,6}n
-.fi
-
-
-would use the following devices:
-
-\fI/dev/rmt/tps0d4n\fR \fI/dev/rmt/tps0d5n\fR \fI/dev/rmt/tps0d6n\fR
-
-.TP
-\fBfile\fR
-This driver emulates a tape device with a set of files in a directory\&. The \fBdriver\-info\fR field must be the name of an existing directory\&. The driver will test for a subdirectory of that named \fBdata\fR and return \fBoffline\fR until it is present\&. When present, the driver uses two files in the \fBdata\fR subdirectory for each tape file\&. One contains the actual data\&. The other contains record length information\&.
-
-The driver uses a file named \fBstatus\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\&.
-
-The \fBlength\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\&.
-
-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 \fBdata\fR in the \fBfile\fR directory to one of the data directories\&. Set the \fBtapetype\fR length to whatever the medium will hold\&.
-
-When \fBAMANDA\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\&.
-
-To read the CD, mount it and create the \fBdata\fR symlink in the \fBfile\fR device directory\&.
-
-.SH "AUTHORIZATION"
-
-.PP
-\fBAMANDA\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 \fBAMANDA\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:
-
-.TP
-\&.rhosts
-Even though \fBAMANDA\fR does not use \fBrsh\fR, it can use \&.rhosts\-style authentication and a \&.rhosts file\&.
-
-.TP
-\&.amandahosts
-This is essentially the same as \&.rhosts authentication except a different file, with almost the same format, is used\&. This is the default mechanism built into \fBAMANDA\fR\&.
-
-The format of the \fI\&.amandahosts\fR file is:
-
-\fBhostname\fR [ \fBusername\fR ]
-
-If \fBusername\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\&.
-
-.TP
-Kerberos
-\fBAMANDA\fR may use the Kerberos authentication system\&. Further information is in the \fBdocs/KERBEROS\fR file that comes with an \fBAMANDA\fR distribution\&.
-
-For Samba access, \fBAMANDA\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 \fBAMANDA\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:
-
-.nf
-
- //some\-pc/home normalpw
- //another\-pc/disk otheruser%otherpw.fi
-With clear text passwords, this file should obviously be tightly protected\&. It only needs to be readable by the \fBAMANDA\fR\-user on the Samba server\&.
-
-You can find further information in the \fBdocs/SAMBA\fR file that comes with an \fBAMANDA\fR distribution\&.
-
-.SH "HOST & DISK EXPRESSION"
-