[tahoe-dev] Potential use for personal backup

[Greg Troxel]

"Zooko Wilcox-O'Hearn" <zooko at zooko.com> writes:

> Thanks for reporting about these backup measurements, Saint Germain!
>
> On Mon, Jun 11, 2012 at 9:06 PM, Saint Germain <saintger at gmail.com> wrote:
>>
>> As a basis for comparison, here are the results for bup:
>> First backup: 12693 Mo in 36mn
>
> Hm, does bup do compression? If not, why wasn't this 24 GB?
>
>> Second backup (after modifications): +37 Mo in 12mn
>
> This is very cool! I want to steal this feature from
> bup/backshift/Low-Bandwidth-File-System and add it to Tahoe-LAFS...

I think that's the wrong approach.  IMHO tahoe-lafs should be a file
system, not a backup program.  I am not aware of any good reasons why
one cannot use tahoe as the place where the bup objects are stored,
except that it results in not having deduplication across
non-cooperating people.

bup stores backup data in a filesystem that it expects to have
reliability and confidentiality properties.  Regular filesystems
(ufs[12], extNfs, etc.) have that property if the disk is protected from
loss and disclosure, and backups to multiple such disks stored safely in
different places, or encrypted and stored in multiple places, more or
less satisfy the goal.   Storing the backup in a tahoe grid should also
work.

So I would suggest that saintger@ try

  mount tahoe into a local mount point using sshfs
    [perhaps pause to pile on to the fuse-first-class tickets :-]
  run bup -d /path/to/tahoe

and see how that goes
-------------- 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/20120614/db913a4d/attachment.pgp>