afserver.conf.8.in

一套客户/服务器模式的备份系统代码,跨平台,支持linux,AIX, IRIX, FreeBSD, Digital Unix (OSF1), Solaris and HP-UX.

.br
  Exabyte:     70
.br
  DLT:         70
.br
.TP
.B Device-Unavailable-Send-Mail-After-Min
If the streaming device is not accessible (i.e. an open or a
tape handling command fails) or another backup server process
is still running, the server process re-tries his attempts
regularly. If it fails longer than the time in minutes
supplied here, an e-mail is sent to the configured user in
charge (see: User To Inform). Supplying 0 means: never send mail.
.TP
.B Device-Unavailable-Give-Up-After-Min
Same as Device-Unavailable-Send-Mail-After-Min, but this time
not an e-mail is sent, but the server process exits silently
leaving a warning in the log file. Supplying 0 means: try
forever, never exit.
.TP
.B Device-Probe Interval
This is the interval in seconds, after that regularly the device
is probed to be ready for reading. Thus after having ejected a
cartridge it is automatically recognized, if a new cartridge has
been inserted. For other media (e.g. exchangeable disks) this may
not be suitable. Supply a 0 in these cases for no probing.
.TP
.B SetFile-Command
This is the (shell-) command to run to position the tape to a
certain file. Usually this is something like a combination
of:  mt -f <device> rewind  and  mt -f <device> fsf <number>.
If the command you are supplying here starts to count with
1 for the first file on tape, you should insert %n for the
<number>. If it starts with 0, replace <number> with %m. If
you don't want to type the devicename again here, you may
write %d instead.
.TP
.B SkipFile-Command
This is the (shell-) command to run to skip over to a file
later on tape. Usually this is something like
 mt -f <device> fsf <number>
Insert %n, where the number of files to skip over must be
supplied in the command, in the example instead of <number>,
and %d, where the device should appear (here: <device>).
.TP
.B Setcart-Command
This is the (shell-) command to run to put a certain
cartridge into the device. If the command you are supplying
here starts to count with 1 for the first cartridge, you
should insert %n in the place, where the cartridge number
must appear. If it starts with 0, replace it with %m. If
you don't want to type the devicename again here, you may
write %d instead. If you don't have a command to perform
this task, don't supply anything here. In this case you must
set your cartridge handling system to sequential mode
(automatically putting the next cartridge in, when the
current one is ejected).
.TP
.B Changecart-Command
This is the (shell-) command to run to eject a cartridge
currently placed inside the streamer device. This is normally
something like  mt -f <device> rewoffl  (but better consult
your man-pages). You have to supply this either if you
have no cartridge handling system (robot) or if you have no
command to set the cartridge directly by number. In the latter
case this package tries to maintain the number of the current
cartridge in a file and to (hopefully) keep it consistent
with the reality. In this case the cartridge handling system
must be configured to sequential mode (automatically putting
the next cartridge in, when the current one is ejected). The
pattern %c, if used in this command, will be replaced with
number of the current cartridge, %n with the number of the
next one, that is expected to be put into the streamer by a
robot in sequential mode. %b can be used instead of %c if
counting of cartridges starts with 0 and not with 1. The
same applies for %m, what means %n minus 1. %d is replaced
with the device name.
.TP
.B Init-Media-Command
The (shell-) command, the server runs before accessing the
storage media for the first time or after changing it. %d
will be replaced with the device. This command can be used
e.g. to automatically mount a removable disk after inserting.
This command might be called several times on the same media,
this has to kept in mind when configuring it.
.TP
.B Erasetape-Command
The (shell-) command to run, if the tape must be erased.
(actually not needed).
.TP
.B Tape-Full-Command
The (shell-) command to run, when a tape is full. %d is
replaced with the device name, %c with the number of the
cartridge, that became full, %n with the number of cycles,
the cartridge has become full until now and %C with the
full path to the configuration file.
.TP
.B User To Inform
If you don't have a cartridge handling system (robot), a
human maintainer must put the appropriate cartridge into the
tape device. If you supply a mail program, an e-mail is sent
to the user given here, which informs him, that and which
cartridge (by number) must be put into the tape device.
If a timespan is configured, after that an automatic e-mail
should be sent due to an unaccessible tape device, it is
directed to this user (see Device-unavail-send-mail-after-min)
.TP
.B Mail-Program
The mail program used to send messages to a human maintainer.
This is done, whenever another cartridge must be put into the
tape device and it can't be done automatically (by a robot or
whatever). If you don't want to type the username again here,
you can instead write %u . The pattern %U will be replaced with
the login name of a current user on the client side, %H with
the name of the client host. If none could be figured out, the
entire word containing %U or %H is deleted from the command.
If you don't want mails to be sent, you may instead supply any
other command, that reads the standard input and does something
reasonable with it, e.g. redirects it to the console:
 cat > /dev/console
.TP
.B Var-Directory
The directory, where varying files should be put in. These
files should not be deleted. The information they contain is
necessary for the server to work properly
.TP
.B Tape-Pos-File
In this file some values are stored, e.g. the number of the
cartridge currently placed inside the streamer device.
.TP
.B Logging-file
Logging information concerning errors or other notable events
is redirected to this file. If the first word of this entry
is starting with @, then logging is directed to the syslog as
well. If there are characters immediately following the @,
this word is used as the syslog identifier, otherwise the
identifier is afbackup. If writing to the syslog is configured,
the rest of the entry is used as additional logging file, if
present.
.TP
.B Status-file
The current status of the server is written to this file. If
it starts with >>, then the file is created and status messages
will be appended to it. Otherwise the file is removed before
writing. %V in the filename is replaced with the configured
Var-Directory
.TP
.B Lock-file
To prevent the server program from being started several times
a lock file is created and this is it's name.
.TP
.B Encryption-Key-Files
Entries specifying files, that contain encryption keys for
authenticating backup clients to the server. Each entry
consists of a filename, optionally followed by a colon : and
a specifier for client selection. If an entry lacks a client
selector, this one will apply for all clients, that are not
matched by any other entry. The client selector is either a
list of comma-separated hostnames, a filename starting with
a slash / containing hostnames one per line, or a command
starting with a bar, that is stripped off before starting
the command. The command gets the current client name as
input on stdin, aside from arguments containing patterns
(see below). If the command returns an exit status of 0,
the client name will match the entry. Entries are separated
by whitespace. If an entry must contain whitespace, it must
be enclosed by double quotes. If colons are needed within
the filenames, they must be escaped using a backslash. Each
key file must contain at least 5 characters and must not
have read permission for group or world. The pattern %H is
replaced with the client name resolved from the IP-address.
%h is similar to %H, but everything from and including the
first dot is stripped off. For more pattern replacements see:
Status-file.
.TP
.B Program-Directory
If you are using the remote start option for backing up
clients, this is the directory, where programs must reside,
that can be started remotely. No other programs can be
started remotely (for security reasons).
.TP
.B Init-Command
Here you may supply a (shell-) command to be run, when the
backup server side wakes up, i.e. the server process starts.
A %p appearing in this command is replaced with the name
of the client, that connected the backup service.
.TP
.B Exit-Command
Here you may supply a (shell-) command to be run, when the
backup server side goes to sleep, i.e. the server process ends.
A %p appearing in this command is replaced with the name
of the client, that connected the backup service.

.SH FILES
.IP @serverlibdir@/@serverconf@
Server configuration file
.IP @serverlogdir@
The directory for logging the server actions
.IP @servervardir@
Some internal state information of the server.
.SH SEE ALSO
afclientconfig(8), xafclientconfig(8), full_backup(8),
incr_backup(8), afverify(8), afrestore(8), xafrestore(8),
update_indexes(8), 
copy_tape(8), afclient.conf(8), afserver(8), afmserver(8),
afserver.conf(8), cartis(8), cartready(8), label_tape(8), tar(1) 
.SH AUTHOR
.B afbackup 
was written by Albert Fluegel ([e-mail]). This manpage was
extracted from the text docs by Christian Meder 
([e-mail]).