programs

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

    -f         force labeling operations without further asking

    -i         inventory the cartridges in the slots specified
                with -S

    -l         list the cartridge locations, together with -S:
                list the contents of the slots (if no slots given:
                of all slots), together with -L: list the contents
                of loadports (specified or all)

    -L <loadp> specify the loadports, that should be part of the
                desired operation. If no loadports are given,
                free ones are searched for when moving

    -m         perform moves of one or more cartridges. These
                must be given using -C. Targets for the moves
                must be given using -S for slots, -L for loadbays,
                -D for drives or -P for somewhere else

    -n <comm>  use the given comment when labeling tapes with -t

    -P <place> Specify the target place for moving or just setting
                a cartridge location. If no place is given on the
                command line, the program will prompt for one

    -r         Together with option -t: delete the labeled cartridges
                from the cartridge database without further asking,
                so they will no longer be protected from overwriting

    -S <slots> Specify the slots, that should be part of the
                desired operation. If no slots are given,
                free ones are searched for when moving

    -s <file>  Use the given file as server configuration file, not
                the default one

    -t         Write labels (`tags') to the cartridges in the slots
                specified with -S

  This command can be used as the SetCartridgeCommand in the
  server configuration. Option -F is required here, cause the
  server itself is already holding a lock on the streamer device,
  thus this command needs not and should not attempt any further
  locking. The entry in the server configuration file should look
  like this:
             /path/to/cart_ctl -F -m -C %n -D

  Files:

  A configuration file to specify the media changer commands must
  be given in the server configuration with parameter
   Changer-Configuration-File
  This file must name the commands, that really perform the moves
  of the cartridges in a changer. A maximum if nine entries can
  be given to specify, how to move a cartridge from or to a slot,
  a drive or a loadbay (3 x 3 = 9). These parameters all have
  names of the form Move-<origin>-To-<target>-Command with origin
  and target being one of slot, drive and loadport, e.g.
   Move-Slot-To-Drive-Command:
  In these commands the following replacements are made:
   %d   the streamer device i.e. drive
   %D   the media changer device
   %n   the origin (e.g. slot) number, if the command starts to
        count with 1
   %m   the origin number, if counting starts with 0
   %N   the target number, if counting starts with 1
   %M   the target number, if counting starts with 0
  Commands, that are not supported for whatever reason, should
  be commented out in this configuration file.
  Two commands can be configured, that print the numbers of free
  slots/loadports to standard output. If there are loadbays, that
  should be used, the command, that lists the free ones, must be
  present. The command listing the free slots must always be
  there. The parameter names for these commands are:
  List-Empty-Slots-Command and List-Empty-Loadports-Command .
  In these commands only the pattern %D is replaced like
  explained above.

  For the most common changer driving commands (mtx and stc),
  appropriate files are included into the distribution. They can
  be used without any modifcation, just comment out the commands,
  your hardware does not support (e.g. moving from slot to slot).

  The cartridge locations database is an ASCII file in the var-
  directory of the server side called cartridge_locations .
  Like all the files there it should not be modified manually.


 $BASEDIR/server/bin/afserver [ <options> ] [ <configuration-file> ]

  The server program. It must be started by the inetd-superdaemon.
  The configuration-file is read as $BASEDIR/server/lib/backup.conf
  if not given explicitly and if not found there the default files
  /etc/buserver.conf, /etc/afbuserver.conf, /etc/afserver.conf and
  /etc/afbackup/server.conf are tried.

  Options:

    -b         Turns off buffering mode. This reduces performance
                but seems to be necessary on some OSes

    -L <locale> Set the locale to the given string. Note, that this
                option might not be honoured due to insufficiencies
                of the gettext implementation on some systems

    -S         Run in slave mode. This option should is used, when
                the program is started as backend for the multi-
                stream server and should not be configured for
                normal startup

  Options for debugging purposes only:

    -D         Enter an infinite loop at startup to be caught
                using a debugger or continue, when a USR1 signal
                is sent to the process

    -s         Don't use secure mode for client requests. No
                authentication is performed

    -l <file>  Use a different logfile than set in the config
                file (see: Parameter Logging-File)

    -x <dir>   Use a different directory for remotely startable
                programs (see: Parameter Program-Directory)


 $BASEDIR/server/bin/afmserver [ options ] [ <configuration-file> ]

  The multi-stream server able to serve several clients in parallel.
  This program works as a protocol multiplexing frontend for the
  normal server, that in turn is started as backend in slave mode.
  For the client side this server looks exactly like the normal
  single stream server, so for them there is nothing special contac-
  ting the multi stream server.
   The clients must pass a unique identifier to the multi stream
  server. Otherwise it cannot distinguish the clients, especially
  when dispatching the data on tape to the clients. By default this
  identifier is the official hostname of the client, that is
  determined from the connection. A client may pass a different
  identifier after having connected and authenticated successfully.

  The options are identical to those of the server program except
  for -S, that is not applicable here, cause the multi-stream
  server doesn't know a slave mode. The other options are passed to
  the server backend (see under afserver above), except for the
  following, that are understood only by afmserver:

    -d         Daemonize. Go into the background and run forever.
                This is the way, the multi stream server can be
                started without using the inetd. -p should be
                supplied when using this option

    -p <port>  The TCP port number or service name, the server
                should bind to. If started via inetd, the inetd
                binds to the port and starts the afmserver connected
                to the port. When started as daemon, the afmserver
                must be told the port to bind to. If not given,
                the service entry afmbackup is used or, if not
                found, the default port 2989


Programs of the client side
---------------------------

 $BASEDIR/client/bin/full_backup

  Run a full backup. The usage:

      full_backup [ -daG ] [ {+-}LBx ] [ <files> <directories> ... ] \
                  [ -C <root-directory> ] [ -F \"<files-to-skip>\" ] \
                  [ -D \"<directories-to-skip>\" ] \
                  [ -c <configuration-file> ] [ -W <identity> ] \
                  [ -h <backuphosts> ] [ -P <backup-ports> ] \
                  [ -I <indexfile-part> ] \
                  [ { -N <num-indexes-to-store> ] | \
                      -O <max-age-of-indexes-to-store-in-days> } ] \
                  [ -z <process-cmd> <unprocess-cmd> ] \
                  [ -Z <built-in-compress-level> ] \
                  [ -s \"<dont-process-patterns>\" ] \
                  [ -X <exclude-list-file> ] [ -l <logfile> ] \
                  [ -i <startup-info-program> ] \
                  [ -b <init-program> ] [ -e <exit-program> ] \
                  [ -k <encryption-key-file> ] \
                  [ -f <filesystem-types> ] \
                  [ -V <var-directory> ] [ -S <cartridge-sets> ] \
                  [ -M <server-message-config> ]

  This program reads the client-side configuration file and runs
  (eventually a part of) a full backup of all files and directories
  specified in the configuration file or on the commandline. It is
  recommended to setup everything in the configuration file and run
  this command without any arguments (same applies for incr_backup).
  If files and/or directories are supplied on the commandline, those
  specified in the configuration file are overridden. Furthermore
  the program then behaves slightly different: If backup parts are
  configured, they are ignored. The timestamp, that is evaluated
  during incremental backup to determine, whether files have been
  modified, is not changed. This behaviour reflects the assumption,
  that supplying files or directories on the commandline is done
  for testing or other temporary purposes. Modifying the timestamp
  would confuse the normal regularly running backup mechanism. In
  these temporary cases the -a option should make sense, see below
  for details. Be also aware of the -C option's meaning. If the name
  of a file is preceded with -r, the contents of the file is stored,
  but not the characteristics of the inode. This is useful for
  saving raw devices. By default, processing is always turned off.
  Using -R forces processing of the contents. Preceding a directory
  name with -m the recursive descent into this directory is limited
  to the filesystem, where the directory resides.
  The names of the files and directories, that are stored, are
  written into logfiles, that comprise of the indexfile-part (-I)
  and the current total backup counter. This counter is incremented
  each time a full backup (part 1) starts. A minimum information
  required to restore after a hard crash having lost everything is
  piped into the startup-info-program (-i). 
  Whether only a part of a full backup is run depends on the setting
  of the parameter NumBackupParts (See: CONFIG). If the configuration
  file is not supplied explicitly, then it is searched for in the
  .../lib-directory and if not found there the files
  /etc/buclient.conf, /etc/afbuclient.conf, /etc/afclient.conf and
  /etc/afbackup/client.conf are tried.
  Commandline options generally override configuration file settings.
  Every option described below (except -c) has a corresponding
  entry in the configuration file, but there are more possible
  settings in the config file.

   -a              Append mode. Do not increment the total backup
                     counter. (See -N)

   {+-}B           Perform per-file processing on the stored files
                     (+B) or not (-B) (See: -F)

   -b <initprog>   Run the given program before attempting a backup.
                     If the command returns an exit status unequal
                     to 0, no backup is performed (see: -e). Not to
                     be mixed up with option -i

   -C <rootdir>    Change to the given directory before starting the
                     backup climbing down into the directories to be
                     stored

   -c <configfile> A different configuration file to use

   -D <skip-dirs>  A list of directory name patterns separated by
                     whitespace to ignore for backup. Several must be
                     put into quotes (See: -F and -X)

   -d              Detach from the terminal when starting

   -e <exitprog>   Run the specified program after finishing. If the
                     command comprises of several words separated by
                     whitespace, it must be put into quotes (See: -i)

   -F <skip-files> A list of filename patterns separated by whitespace
                     to ignore for backup. Several must be put into
                     quotes (See: -D and -X)

   -f <fs-types>   A list of filesystem types, separated by whitespace
                     and/or commas. The type names can be prefixed
                     with a plus, what is identical with no prefix,
                     with a dash - or a slash / . No prefix or a plus
                     means, that only files in filesystems of the
                     given type are saved, no others. A minus means,