rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[rdiff-backup-users] Version 0.11.2 released


From: Ben Escoto
Subject: [rdiff-backup-users] Version 0.11.2 released
Date: Sat, 01 Mar 2003 22:05:01 -0800

This version was mainly about responding to unexpected errors during
the session.  In particular rdiff-backup now has a relatively
principled way of handling recoverable and unrecoverable errors (see
the error policy file mentioned below on the web page).  Input is as
always (as usual?) appreciated, so post to the list if you have
comments.

    One cool thing is that rdiff-backup now has session level
atomicity, so that an aborted backup is "undone" later so it looks
like it never existed.  You can even undo completed backups, although
this functionality is not exposed.

    Anyway, here is the relevant portion of the changelog:


New in v0.11.2 (2003/03/01)
---------------------------

Fixed seg fault bug reported by a couple sparc/openbsd users.  Thanks
to Dave Steinberg for giving me an account on his system for testing.

Re-enabled --windows-mode and filename quoting.

Fixed selection bug:  In 0.11.1, files which were included in one
backup would be automatically included in the next.  Now you can
include/exclude files session-by-session.

Fixed ownership compare bug:  In 0.11.1, backups where the destination
side was not root would preserve ownership information by recording it
in the metadata file.  However, mere ownership changes would not
trigger creation of new increments.  This has been fixed.

Added the --no-inode-compare switch.  You probably don't need to use
it though.

If a special file cannot be created on the destination side, a 0
length regular file will be written instead as a placeholder.
(Restores should work fine because of the metadata file.)

Yet another error handling strategy (hopefully this is the last one
for a while, because this stuff isn't very exciting, and takes a long
time to write):

        All recoverable errors are classified into one of three groups:
        ListErrors, UpdateErrors, and SpecialFileErrors.  rdiff-backup's
        reaction to each error is more formally defined (see the error
        policy page, currently at
        http://rdiff-backup.stanford.edu/error_policy.html).

        rdiff-backup makes no attempt to recover or clean up after
        unrecoverable errors.

        However, it now uses fsync() to increment the destination
        directory in a reversable way.  If there is an error, the next
        backup will regress the destination directory into its state
        before the aborted backup.

        The above process can be done without a backup with the
        --check-destination-dir option.

Improved error logging.  Instead of the old haphazard reporting
method, which sometimes didn't indicate the file an error occurred on,
now all recoverable errors are reported in a standard format and also
written to the error_log.<time>.data file in the rdiff-backup-data
directory.  Thanks to Dean Gaudet and others for repeatedly bugging me
about this.


-- 
Ben Escoto

Attachment: pgpWbmNOnUySI.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]