Re: [Duplicity-team] [Question #150909]: reverse diffs
Question #150909 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150909 Status: Answered = Open ceg is still having a problem: uh, so duplicity is no chunky bacon. ;-) Doing unnecessary full backups of hundreds of GB if only a couple MB have changed is just too unfortunate. But having all data stored in a single data stream that causes everything behind a single corruption to be lost, well, many thanks edso for pointing that out! Shouldn't duplicity chunk the files to volumes first and then compress and gpg them? Well, probably just switch from using .tar to .dar for various reasons. Dar seems much better then .tar and already supports reduncancy checksumming etc. -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
Re: [Duplicity-team] [Question #150909]: reverse diffs
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. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
Re: [Duplicity-team] [Question #150909]: reverse diffs
Question #150909 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150909 Status: Open = Answered edso proposed the following answer: On 30.03.2011 10:08, ceg wrote: 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! no problem 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. duplicity diffs are actually a tgz/gpg'd sum of all rsync detected changes in the backup source. They are only split into volumes to get handy uniform sized chunks for backup repositories that might need it (e.g. gmail). so actually there is no possibility of renaming/reusing anything. duplicity has to go through the chain and reassemble your data. if corruption occured, then at least some data is definitely lost. there are loose plans to integrate redundancy checksumming, but that is far future. for now the suggested way to deal with this weakness is to do periodically fulls to keep chains short and the probability of data loss small. ede/duply.net -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
[Duplicity-team] [Question #150909]: reverse diffs
New question #150909 on Duplicity: https://answers.launchpad.net/duplicity/+question/150909 Could duplicity keep reverse diffs, so the latest backup does not depnend on an old backkup plus a chain of diffs? -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
Re: [Duplicity-team] [Question #150909]: reverse diffs
Question #150909 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150909 Status: Open = Answered edso proposed the following answer: On 29.03.2011 17:14, ceg wrote: New question #150909 on Duplicity: https://answers.launchpad.net/duplicity/+question/150909 Could duplicity keep reverse diffs, so the latest backup does not depnend on an old backkup plus a chain of diffs? if you mean if duplicity can merge older full/diffs into a new full - no. ede/duply.net -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
Re: [Duplicity-team] [Question #150909]: reverse diffs
Question #150909 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150909 Status: Answered = Open ceg is still having a problem: merge older full/diffs into a new full I guess that is only part of what rdiff-backup does (on the remote site). I'd like duplicity to keep a current full plus reverse diffs like rdiff-backup (in a chain) where this makes sense (local filesystem, trusted local machine) -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
