manual.txt

Linux系统备份源代码 可基于用户自定义策略实现系统、应用数据备份

    SMTP servers is a strange piece of software.. Some requires a correct
    host and domainname to be given when sending mail, others need only
    the domainname and for some, it does not matter at all.
    If you receive errors when trying to send a report, it is most likely because
    the combination of your hostname and domainname are bad... Sitback will
    try two combinations.

    You might find that providing something like 'localhost.localdomain' is
    rejected by the smtp server, in that case, set a domainname for your host
    which can be resolved via dns.. (for ex. your isp's domainname, being a
    customer there grants you that right.. i guess?)..

    If the above does not help, run sitback once more, with the '-g' switch..
    Include the file '~/.sitback/sitback.debug', and the output from the
    commands hostname and domainname in a mail to me.

SMTPHOST
    If you do not specify an smtp host (smtp mail-server), Sitback assumes
    that you have a local sendmail listening on port 25, capable of doing
    standard SMTP. Else add a mailserver..

    F.ex..:
      'SMTPHOST=mail.some.host'.

SMTPUSER & SMTPPASS
    If your smtp server requires authentication. Put your username
    and password in the script with these keywords. Smtp authentication
    will then automatically be attempted.

    Warning: Like with the SMBPASSWORD..  You have a clear text
             password in the script, so make sure no unauthorized
             users can read the script..
             
INCREMENTAL
    Update the archive (incremental backup) instead of a full backup.

TYPE
    Sitback can create several different types of archives or backup's.

    TYPE=TAR (default)
      This is how sitback has always been working. It takes a set of files and/or
      directory's and creates a tar/tar.gz/tar.bz2/tar.Z file on some local or
      remote device or filesystem.

      ARCHIVE is either the name of the raw device that tar writes the data to,
      or the name of the file that tar creates with the archive..

    TYPE=TARCDR / TYPE=TARCDRW
      Sitback creates a standard tar/tar.gz/tar.bz2/tar.Z archive, and writes it
      to a blank cd. Use TARCDRW with a rewriteable cd, sitback will blank it
      before writing the archive.
      The Iso will contain a single file with the name 'archive.tar[.gz|bz2|Z]', and
      a timestamp file.

      Please note that a TARCDRW disc can not be mounted with a normal cd
      drive because rewriteable cd's are not fixated. You can add the option
      FIXATE to fixate the disc, thus make it readable by regular cd drives, but
      that prevents you from blanking (reusing) the cd-rw again...

      ARCHIVE must be the scsi-id where the cd writer is found.. Use
      'cdrecord -scanbus' to get this number.. (or check with your normal cd
      writing software).

      F.ex..:
        ARCHIVE=0,0,0

      Please note that these modes will generate temporary local files which
      can take up twice as much space as the target cd (creation of an
      750MB cd may require 1.5GB of local storage). The option
      'CD ON THE FLY' can reduce the amount of required temporary space.
      Please also check the 'TEMP' option.

    TYPE=TARISO
      Sitback creates a standard tar/tar.gz/tar.bz2/tar.Z archive, and writes
      it to a iso image. The Iso will contain a single file with the name
      'archive.tar[.gz|bz2|Z]'.

      ARCHIVE is the name of the name of the iso file that tar creates.

    TYPE=ZIP
      Create a zip archive on a disc or a device..
      ARCHIVE is either the name of the raw device that zip writes the data to,
      or the name of the file that zip creates with the archive..

    TYPE=ZIPCDR / TYPE=ZIPCDRW
      Sitback creates a standard zip archive, and writes it to a blank cd. Use
      ZIPCDRW with a rewriteable cd, sitback will blank it before writing the
      archive.
      The Iso will contain a single file with the name 'archive.zip'. Please note
      that a ZIPCDRW disc can not be mounted with a normal cd drive because
      rewriteable cd's are not fixated. You can add the option FIXATE to fixate
      the disc, thus make it readable by regular cd drives, but that prevents you
      from blanking (reusing) the cd-rw again...
      ARCHIVE must be the scsi-id where the cd writer is found.. Use
      'cdrecord -scanbus' to get this number.. (or check with your normal cd
      writing software).

      E.x.   ARCHIVE=0,0,0

      Please note that these modes will generate temporary local files which can
      take up twice as much space as the target cd (creation of an 750MB cd may
      require 1.5GB of local storage). The option 'CD ON THE FLY' can reduce the
      amount of required temporary space. Please also check the 'TEMP' option.

    TYPE=ZIPISO
      Sitback creates a standard zip archive, and writes it to a iso image. The Iso
      will contain a single file with the name 'archive.zip'.

      ARCHIVE is the name of the iso file that zip/mkisofs creates.

    TYPE=CDR & TYPE=CDRW
      With these modes, sitback copies files and directory's directly to a blank cd.
      They are not stored in a tar archive, and there is no compression. This mode
      can be used to create distribution cd's from a local disk, or just plain backup's .
      CDR writes to a blank cd, and CDRW blanks a cd-rw, then writes the data.
      Please note that a TARCDRW disc can not be mounted with a normal cd drive
      because rewriteable cd's are not fixated. You can add the option FIXATE to
      fixate the disc, thus make it readable by regular cd drives, but that prevents
      you from blanking (reusing) the cd-rw again...

      ARCHIVE must be the scsi-id where the cd writer is found.. Use
      'cdrecord -scanbus' to get this number.. (or check with your normal cd
      writing software)

      E.x.   ARCHIVE=0,0,0

      Please note that these modes will generate temporary local files which can
      take up as much space as the target cd (creation of an 800MB cd may
      require 800MB of local storage). The option 'CD ON THE FLY' can remove the
      need for temporary space. Please also check the 'TEMP' option.

      Please also be aware of the fact that this type of backups can fail if the
      directory's included in the backup contains filenames that can not be
      truncated/modified to ensure unique filenames in the joliet list of files needed
      to support long filenames for msdos/vfat partitions and systems. (This does
      not change the original filenames that you will see when using the cd on a
      unix system..). If your backup fails due to this type of error, create a
      TARCDR[W] archive instead..

    TYPE=ISO
      Sitback copies the selected files and/or directory's to an iso image file.
      But the image is not written to a blank cd. ARCHIVE is the name of the file
      that is created.

      Please also be aware of the fact that this type of backups can fail if the
      directory's included in the backup contains filenames that can not be
      truncated/modified to ensure unique filenames in the joliet list of files needed
      to support long filenames for msdos/vfat partitions and systems.
      (This does not change the original filenames that you will see when using
      the cd on a unix system..). If your backup fails due to this type of error,
      create a TARISO archive instead..

    TYPE=FILECOPY
      Sitback copies the selected files and/or directory's to a new location on a
      local or remote filesystem. ARCHIVE is the directory name of the top-level
      directory with the copy of the files..

SPEED
    If you are creating cd archives, you can specify at which speed the cdwriter
    should operate.. This value is passed directly to 'cdrecord'.. If you do not
    specify any speed, the 'speed' argument is not given to 'cdrecord', causing
    'cdrecord' to use some default speed (most likely the fastest speed supported
    by your writer.)

BUFFERSIZE
    If you are creating a cd, you can set a specific io-buffer/fifo size. for 'cdrecord'.
    Please check man cdrecord under the fs=# option for possible formats.. Most
    likely, you will use something like BUFFERSIZE=4m (set the io-buffer/fifo size
    to 4MB)

EJECT
    If you are creating a cd, you can get it ejected after the write procedure has
    finished.. EJECT=YES does that, EJECT=NO does not eject the cd, but that is
    default...

FIXATE
    If you are using a cd-rw for the backup, sitback will not fixate the disk. Usually,
    on linux, cd-rw's that are not fixated can only be read by a cd-writer
    supporting cd-rw's.. So if, for some obscure reason, you want sitback to fixate
    the (more expensive) cd-rw after having created the archive, include this
    keyword in the script..

    The keyword has no meaning for other types than CDRW.. (normal cd's are
    always fixated)

CD ON THE FLY
    If you are creating a cd archive, use this option to write the cd directory
    without creating a temporary iso image first.. This requires that your machine
    has enough power and I/O throughput so that buffers will not be empty at
    any time during the write..

    Also important, if using this option, make sure that you can execute a new
    subshell with the command sh (most systems is set up this way, but if not,
    create a symlink in '/usr/bin' to your shell)

ADD TO ROOT
    This option only works with regular iso based archives (ISO/CDR/CDRW).

    Instead of adding targets with full path, targets are added to the root of the
    cd. This prevents restoring the files to there original location, but helps if
    you just want to make a plain cd with a set of files or directory's.
    (Please also see the next section in that case..)

NO INFO
    This option only works with regular iso based archives (ISO/CDR/CDRW).
    Add this option to the script if you do not want the 'sitback.*' file's
    which contains various info used by sitback during restore and list operations.

TEMP
    Most of the temporary files created while running sitback is very small, but
    a few files may grow to sizes that can exhaust your '/home' partition's free
    space.. If you are creating a cd backup, and not using the 'CD ON THE FLY'
    option (your machine may not be powerfull enough for this to work safely),
    you need enough storage under /home/ to
    hold the temporary iso image. For a 800MB cd, that is 800MB. And it can get
    even worse, if you are creating a tar archive on a cd and not using the
    'CD ON THE FLY' option. First the tar (tar.gz) archive is created, then the
    local iso image is created.. So for a 800 MB cd, worst case, you must have
    1.6GB of free storage for the operation to succeed..

    If you do not have all this free space on you /home partition, then use the
    TEMP option to set a tempfile location that has enough free space for the
    temporary images and archives, f.ex. 'TEMP=/opt/tmpfiles'.

BUFFERSIZE
    Set a specific buffersize for cdrecord. Only needed for a few writers/devices.
    (onTrack streamers need this).

UNATTENDED
    Run a normal (not daemon) sitback session without requests for keypresses.
    Especially usefull for running one-time sessions from scripts. (cron, etc)



Sitback takes various switches on the command-line. You might f.ex. disable some
features enabled in the script, or enable something, disabled in the script, such as compression.

As always, by typing sitback --help you will get all the help you need to find the
right switch or syntax..

Sitback can only handle 1 script per instance. But if you want parallel versions of
sitback to run, f.ex. to run a full backup monday, wednesday and friday and
incremental backups on tuesday and thursday, You must first start one instance,
then allow a few seconds of startup time, then start the next instance with
the '--skip-lock' option.. It is very important that the scripts do not execute at
the same time, that could produce some pretty strange results..



Backup operation
    sitback [options] scriptname

  -a
    Use this archive or device instead of ARCHIVE from the script.
    Please see the above section for info on remote devices.

  -c [BZIP2|GZIP|COMPRESS]
    Compress archive.
    If you want to control wich compression tools is used, give the tool-name here.

  -d
    Run as daemon instead of just a single run

  -e
    Dont verify the archive after backup.

  -h app.
    Use the application 'app' for remote shell access if the archive device is a
    remote device.. Usually, this would be either 'rsh' or 'ssh', but others will work
    too, as long as they has same usage as rsh..

  -i archive-id
    Set the archive id to this string. (no blank spaces is allowed). The archive-id
    is updated or added, if no current archive exists, f.ex. on a tape, a archive is
    created. In any case, operation is stopped after updating the archive id so
    that the. archive is empty apart from the info

  -j 'script or command'
    Run script or command before backup

  -k 'script or command'
    Run script or command after backup

  -m [count][K|M]
    Create multiple volumes. If a byte-count is given, volumes will be no larger
    than #count# bytes. 'K' or 'M' may be appended to indicate that count is
    in KB or MB. When no modifier is appended, the count should be an equal
    number of 1024B blocks. If no length is given, multiple volumes is only created
    if the first device has no more space on it.. The user will the be prompted for
    a new tape/disk. Multiple volumes is not allowed in daemon mode. Verification
    of backup is not possible if compression is used, the -e switch is then silently
    appended.

  -n
    Ignore the time-string, run now.

  -o
    Follow symlinks.

  -p
    Adjust nice level. Regular users can decrease the priority in the range 0 to 19,
    root can increase or decrease the priority in the range -20 to 19

  -q
    Create a copy of the files and directorys selected as targets. The
    archivename/devicename given will be used as the name of the directory