programs

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

                    to be a different one than it is in fact, this
                    option must be used
 
    -z <z> <uz>   The commands to use for process and unprocess. If
                    a command comprises of several words, it must be
                    put in quotes

    -Z <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

  I suggest to run restore with the -l option before really going
  to restore anything. So you see, what files will be generated,
  maybe overwriting existing ones unintendedly (or use option -m).


 $BASEDIR/client/bin/afverify

  Run a verify of a previous backup. The usage:

     afverify [ -lav ] [ -c <configuration-file> ] \
              [ -<past-run-no>[.<past-backup-no>] ] \
              [ -h <backuphosts> ] [ -P <backup-ports> ] \
              [ -C <root-directory> ] [ -S <cartridge-sets> ] \
              [ -I <indexfile-part> ] [ -V <var-directory> ] \
              [ -k <encryption-key-file> ] [ -W <identity> ] \
              [ -z <process-cmd> <unprocess-cmd> ] \
              [ -Z <built-in-compress-level> ] \
              [ -M <server-message-config> ]

  Without any arguments, this program runs a verify over the
  previously written backup. This may either be a full or an
  incremental backup, only the contents of the very previous
  run are used. All found differences are reported.
   Though it is not considered to make too much sense, it is
  also provided, that files and directories saved during a run
  before the previous one can be checked. This can be done
  supplying the <past-backup-specifier>. If this is a simple
  number, it counts back from the previous full or incremental
  backup of the same total backup number (this number is increased
  each run of the full_backup-command, not by subsequent
  incremental backups). -1 means, that the backup before the
  previous one is checked and so on. If the contents of a previous
  total backup run should be checked, the following form may
  be used: -<previous-run>.<previous-total-backup>, where
  <previous-total-backup> counts back from the current total backup
  number and <previous-run> counts back from the last backup
  (incremental or full) run among the previous total. previous-run
  may be 0 here. E.g. verify -0.1 checks the files saved during
  the last run of the previous total backup. Run afverify with
  option -l, optionally -a or -<prev-total-backup> to get a list
  of backups available for verify.

    -a            Together with -l list the available backups from
                    all indexes and not only the most recent one

    -C <root-dir> Change to the given root-directory before verifying
                    files instead of the one specified in the client
                    side configuration file.

    -c <conffile> Use the given file for configuration information

    -h <hostnames> Use the given list of hosts as backup servers. This
                    list is used only, if no hostname information can
                    be found as associated with the current filesystem
                    entry, that should be verified. The first host in
                    this list is the default server, if no hostname
                    information at all can be found. The hostnames in
                    this list can be separated by whitespace and/or
                    commas

    -I <idx-prefix> The first part of the filename, the names of the
                    stored files and directories can be found. The
                    current total backup number is appended (that
                    increments each start of a full backup). If these
                    files undergo processing, .z is appended

   -M <svrmsg-conf> The configuration to output messages from the server,
                     that normally are sent only via mail to a maintainer.
                     The first word consisting of the letters b r v and c
                     tells, whether to output messages during backup,
                     restore, verify and copy-tape, respecively. The next
                     words must name the service name or port number of
                     the single stream servers, related to the option -P .
                     For each multi stream service configured with -P or
                     in the configuration file, the respective single
                     stream service must be given here

    -k <file>     Use the contents of the given file as encryption
                    key for authenticating to the server

    -l            Don't actually verify, but print summary information
                    about available backups, that can be verified or
                    restored from, prefixed with the arguments, that
                    may be supplied as -<past-run-no>[.<past-backup-no>]

    -P <portnos>  The list of port numbers for the backup servers
                    either configured in the parameter file or supplied
                    with the -h option. This list is used only, if no
                    port number information can be found as associated
                    with the current filesystem entry, that should be
                    verified. The port numbers supplied here are asso-
                    ciated with the backup server names by position.
                    The port numbers in this list can be separated by
                    whitespace and/or commas

    -V <var-dir>  The directory, where varying files are put

    -v            Verbose mode: print information records on tape and
                     the names of the checked files during operation

    -W <id>       Identify as <id> to the server. This is needed when
                     connecting a multi-stream server to distinguish
                     between the clients. Default is the official
                     hostname of the client. If the client should fake
                     to be a different one than it is in fact, this
                     option must be used
 
    -z <z> <uz>   The commands to use for process and unprocess. If
                    a command comprises of several words, it must be
                    put in quotes

    -Z <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

  In my opinion a verify makes only sense immediately following
  an incremental or full backup with the purpose to check, whether
  the files and directories did not get corrupt on the storage
  media. If you want to do this (via cron or however), keep in
  mind, that the verify takes at least the same time as the
  backup itself. If you have a huge amount of data to save, the
  additional verify might run you into time consumtion problems.


 $BASEDIR/client/bin/copy_tape

  Make a duplicate of a tape. The usage:

     copy_tape [ -v ] [ -c <configuration-file> ] \
                 [ -l <logfile> ] [ -T <tmpdir> ] \
                 [ -M <server-message-config> ] \
                 [ -h <source-server> ] [ -P <source-serverport> ] \
                 [ -C <source-cartridge> ] [ -F <tape-filenumber> ] \
                 [ -k <source-encryption-key-file> ] \
                 [ -D \
                  [ -h <target-server> ] [ -P <target-serverport> ] \
                  [ -C <target-cartridge> ] \
                  [ -k <target-encryption-key-file> ] ]

  This command connects to one or two backup servers and makes
  an identical copy of a tape to another one. The tape label
  is rewritten, so that the destination tape keeps it's primary
  cartridge number, but gets the number of the source tape as
  secondary number. Thus it can be used instead of the tape
  with that primary number. In fact both numbers are accepted
  for backup, restore or other operations except the copy_tape
  operation itself. Recursively copying an already duplicated
  tape does not further change the secondary cartridge number,
  so e.g. any copy of cartridge number 3 will be usable as such.
  Copying cartridge 3 to cartridge 5 and then 5 to 8 does not
  make cartridge number 8 usable as cartridge 5, but still as
  cartridge number 3. When the backup server sees a cartridge
  with the wrong primary number, but the correct secondary
  number, this cartridge is accepted, but a warning is written
  to the serverside log. The defaults for the copying source are
  taken from the client side configuration file. Default source
  cartridge is the one currently loaded in the drive on the
  server, that will be asked for this information. If no target
  parameters are supplied, they get the values of the appropriate
  source parameters as default. So if no arguments are supplied,
  the current tape would be copied to itself, what is prevented
  while printing an error message. Target (or: destination)
  parameters must always be following the -D option, source
  parameters must be supplied in an earlier position. If the
  source tape is operated by a different server than the target,
  copying goes straight from one to the other. As two servers
  (with a different port number) can reside on one host, this
  process does not necessarily imply a network connection.
  If source and target tape are handled by the same server, the
  data to be copied must be stored somewhere inbetween. For this
  purpose a temporary directory is created on the client, where
  this program is started, usually in /tmp or /var/tmp (see:
  tmpnam(3)). The filesystem, where this directory lives, must
  have a free capacity of at least the largest occurring tape
  file. This maximum tape file size is configured on the server
  side by the parameter MaxBytesPerFile (see: afserver.conf(8)).
  If there is not enough space, the duplication of the tape
  fails. The copying program writes as many tape files to disk
  as it can, while a certain amount will remain free. Then it
  ejects the source cartridge and loads the target cartridge.
  Now the files in the temporary directory are written to the
  target tape while immediately removing files, that are no
  longer needed. The more space is available in the temporary
  directory, the fewer cartridge loads/ejects are necessary.

   -C <cartridge>    The number of the cartridge to use as copying
                      source or target (depends on argument position:
                      before or behind -D).

   -c <configfile>   Use the given file for configuration information

   -F <tapefilenum>  If reading and writing should not start at the
                      beginning of the tape, but at the tape file with
                      the given number. This can avoid the overhead of
                      copying entire tapes, when only some tape files
                      have been appended

   -h <hostname>     The name of the backup server host, where the
                       source or target cartridge is handled,
                       respectively

   -k <file>         Use the contents of the given file as encryption
                      key for authenticating to the server, where the
                      source or target cartridge is handled,
                      respectively

   -l <logfile>      A file to write log information to

   -M <svrmsg-conf> The configuration to output messages from the server,
                     that normally are sent only via mail to a maintainer.
                     The first word consisting of the letters b r v and c
                     tells, whether to output messages during backup,
                     restore, verify and copy-tape, respecively. The next
                     words must name the service name or port number of
                     the single stream servers, related to the option -P .
                     For each multi stream service configured with -P or
                     in the configuration file, the respective single
                     stream service must be given here

   -P <portnum>      The port number of the backup server on the
                      backup server host, where the source or target
                      cartridge is handled

   -v                Verbose option, tell more about what is going on


 $BASEDIR/client/bin/update_indexes

  clean indexes from erased tapes

    update_indexes [ -v ]  [ -c <configuration-file> ]
                   [ -h <backuphosts> ] [ -P <backup-ports> ]
                   [ -I <indexfile-part> ] [ -V <var-directory> ]
                   [ -k <encryption-key-file> ] [ -W <identity> ]
                   [ -z <process-cmd> <unprocess-cmd> ]
                   [ -Z <built-in-compress-level> ]

  This command asks all the servers, which tapes are considered
  precious for the client, it is run on. If the server will tell
  fewer tapes than the client has in mind, then the tapes, that
  the server omitted, have been erased on the server side. Now
  those entries will be removed from the client's indexes, who
  list the erased tapes as backup location.
  This command may be installed setuid root, so normal users can