[tahoe-dev] Potential use for personal backup

[Greg Troxel]

Shawn Willden <shawn at willden.org> writes:

> On Tue, May 22, 2012 at 9:52 AM, Saint Germain <saintger at gmail.com> wrote:
>
>> On 22 May 2012 17:44, Shawn Willden <shawn at willden.org> wrote:
>> >> So tahoe-LAFS works in that case basically as Dropbox synchronisation
>> >> (with the encryption).
>> >> Is there some kind of optimization which only transfer modified parts
>> >> to the other nodes, or is the whole file transfer each time it is
>> >> modified ? Especially for VM.
>> >
>> > It's whole-file.
>> >
>>
>> Ok, definitely a problem for VM then.
>
> Probably.  I can think of some workarounds, such as snapshotting your VMs,
> which causes changes to be written to a small differences file leaving the
> bulk of the virtual storage unmodified.  But, no, Tahoe isn't particularly
> well suited to backing up large files.

One thing to think about is combining something like bup and tahoe.  I
haven't actually tried this yet, but it seems promising.  bup does
sub-file-level deduplication and works with VM images, and has a
write-only git-compatible packfile format, reusing pointers to previous
packs.  So the bup write pattern should fit with tahoe.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120522/4ff26f89/attachment.asc>