full_backup.8.in

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

option must be used. This flag can also be useful
e.g. to explicitly store the serverside
var-directory, that is crucial for restore and should be
saved seperately after all other backup clients are done.
.TP
.B -X <excl-file>
The name of a file, that may exist in any directory
containing a list of filename patterns, one per
line. All files and directories in that directory
matching one of the patterns are exluded from
backup (See: -D and -F)
.TP
.B {+-}x
Write CRC32 checksums for each file to tape (+x) or don't
do this (-x). This option is ignored, if built-in compression
is selected, cause then CRC32 checksumming is already performed
.TP
.B -Z <built-in-compress-level>
If built-in compression should be used, the level
can be supplied here. If commands to process and
unprocess are also supplied with option -z, then
data is first processed by the process command,
then by built-in compression. During uncompress it
works the other way round
.TP
.B -z <proccmd> <unproccmd>
The commands to use for process and unprocess. If
a command comprises of several words, it must be
put in quotes
.PP
A table of corresponding command line options and configuration
file entries, (subsets) accepted by full_backup, incr_backup,
restore, verify:
.TP
.B Option
Client configuration file parameter name
.TP
.B +B -B
ProcessBackupedFiles
.TP
.B -C
RootDirectory
.TP
.B -D
DirsToSkip
.TP
.B -e
ExitProgram
.TP
.B -F
FilesToSkip
.TP
.B -f
FilesystemTypes
.TP
.B -h
BackupHost
.TP
.B -I
IndexFilePart
.TP
.B -i
StartupInfoProgram
.TP
.B -k
EncryptionKeyFile
.TP
.B -l
LoggingFile
.TP
.B +L -L
ProcessLogfiles
.TP
.B -N
NumIndexesToStore
.TP
.B -P
BackupPort
.TP
.B -S
CartridgeSet
.TP
.B -s
DoNotProcess
.TP
.B -V
VarDirectory
.TP
.B -W
ClientIdentifier
.TP
.B -X
ExcludeListFile
.TP
.B -x
WriteChecksums
.TP
.B -z
ProcessCmd UnprocessCmd
.TP
.B -Z
Built-inCompressLevel
.SH SIGNALS
When receiving SIGHUP or a single SIGINT (i.e. keyboard Ctrl-C)
this program tries to process all pending writes to the server
before terminating. That is, if the server is currently not
ready to process requests, this program will wait until the
server is done or terminates unexpectedly, what will break the
connection to all clients. Any connection breakdown will cause
a SIGPIPE and thus make a client terminate prematurely. If this
program should not wait for the server to terminate properly,
but shut down as soon as a consistent status of the client's
local persistent data can be achieved, SIGQUIT (== Ctrl-\\) or
SIGABRT must be sent (once) or SIGINT (== Ctrl-C) 3 times within
2 seconds. Pressing Ctrl-C the second time a respective hint is
written to the user. The same can be achieved by sending SIGTERM,
which is the default using the kill(1) command. This signal is
typically sent to all processes, when a Unix-system goes down in
a controlled manner without crashing or fast halt. When SIGINT
is received and standard input of this program is not a TTY, the
immediate shutdown without waiting for the server is attempted
as well. A shutdown like this can be expected to finish quite
surely within one second.
.SH FILES
.IP @clientconfdir@/@clientconf@
Client configuration file
.IP @clientlogdir@
The directory for logging the client backups
.IP @clientvardir@
Some internal state information of the client backups.
.IP @clientvardir@/num
Here the current total number of backups is stored.
The total number of backups is incremented each time
a full backup finishes successfully, if not the append
mode (option -a) is selected or files and directories
are explicitly supplied as arguments. This case is
considered an exceptional storing of files, that should
not affect counters or timestamps
.IP @clientvardir@/part
If present, it contains the number of the backup part
that has recently started. Full backups can be split
in pieces if a complete run would take too much time.
This can be configured with the parameters
NumBackupParts, DirsToBackup1, ...
.IP @clientvardir@/oldmark
The Modification time of this empty file serves as
memory for the timestamp, when any full or incremental
backup has started before. This should be handled in
the file explained next, but due to backward compati-
bility issues i will not change this (historical error
coming from the earlier used scripts for backup and
the use of the find-command with option -newer)
.IP @clientvardir@/newmark
During backup a file holding the timestamp of the
backup starting time. The reason, why this timestamp
is kept in the filesystem is safety against program
crashes
.IP @clientvardir@/level_timestamps
This file contains the timestamps for the backup
levels. Each line has the following format:
 <backup-level>: <incr-backup-starting-time>
For each used backup level and the full backup a line
will be maintained in this file
.IP @clientvardir@/save_entries
This file holds the patterns of all configuration
entries in DirsToBackup, DirsToBackup1, ...
for use in subsequent backups. If new entries will be
configured, this file allows to automatically switch
to full backup from incremental backup, when a new
entry in the configuration file is found
.IP @clientvardir@/needed_tapes
This file contains a list of tapes needed for full
restore of all files listed in existing filename list
files (i.e. index). The number of these files depends
on the clientside parameter NumIndexesToStore. After
each backup (full or incremental or X-level) a line
is added to this file or an existing one is extended
to contain the current backup counter and a list of
backup levels with the cartridge numbers used during
write associated. The format is:
 <backup-counter>: <backup-level>><tape-list> [ <backup-level>><tape-list> ... ]
When running an incremental or differential backup
supplying the option -H, entries with a level lower
than the current one (or in differential mode equal
to the previous) are removed from this list. Thus the
tapes from these entries are permitted to be written
again (often called "recycled")
.IP @clientvardir@/start_positions
Here for each full or incremental backup within the
range required by the parameter NumIndexesToStore
the information to retrieve all the data is stored.
Each line has the format
 <backup-counter>: <backup-server> <backup-service> <cartridge-number> <file-number>
Having this information everything can be restored in
case all other data is lost
.IP @clientvardir@/server_ids
The information, which server network address has which
server-ID assiciated. The first two columns contain the
hostname and port number, the third the server-ID
.IP @clientvardir@/index_ages
For each existing index file, this file contains a
line with the index number in the beginning, followed
by a colon and the timestamp of the last modification
of that index in seconds since epoch (1.1.1970 0:00).
This file is evaluated, if the client side parameter
DaysToStoreIndexes is set.
.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), 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]).