|
From: | Colin Ryan |
Subject: | [Duplicity-talk] Rollup Functionality and Parity? |
Date: | Mon, 18 Aug 2008 11:59:26 -0400 |
User-agent: | Thunderbird 2.0.0.16 (Windows/20080708) |
My concern about the latter is should even one incremental in the chain become corrupt everything from that point on (I assume) is unrecoverable. So I was wondering if there is any technique that could be used to "periodically" roll up the incrementals on the remote respository side into a full to create an "new single full" which contains all the incrementals, but that would allow duplicity to simply continue on with incremental backups on the client end. This would simply - for what it's worth - reduce the number of files that must be 100% intact but would allow one to always run duplicity in just incremental mode while periodically generating a full.
As a side note has anyone put any thought to using Par2 parity files on the tar files that duplicity generates. Yes this would increase the back end storage but would allow for recoverability of the file provided data corruption was 5-10-20% of the file.
Not sure I've explained my thoughts clearly but...
[Prev in Thread] | Current Thread | [Next in Thread] |