duplicity-team team mailing list archive

[ceg <question150909@xxxxxxxxxxxxxxxxxxxxx>]

Question #150909 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/150909

    Status: Answered => Open

ceg is still having a problem:
Thanks for your reply edso!

>From man rdiff-backup (just for the casual reader):

"The target directory ends up a copy (mirror) of the
       source directory, but extra reverse diffs are stored in a special  sub-
       directory of that target directory, so you can still recover files lost
       some time ago."

Since the current data is not stored in the form of an old full backup +
a chain of diffs, a currupted diff in the chain wont't affect your
ability to recover your current data. Instead, you always have a copy
(mirror) of your current data, and it's only the older versions that are
only available by applying the (reverse, or going back) diffs, and
having an increased risk of file corruption in the chain.

Since duplicity, keeps volumes it could rename any volume that has not
changed to be part of the current state. If a file in the volume has
changed, it could produce a new volume and then calculate a reverse diff
on the volume.

Hopefully, with this duplicity should also be able to omit very long and
slow full backups (with large slowly changing datasets) every x backups
and when purging older versions.

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.