[tahoe-dev] Potential use for personal backup

[Saint Germain]

On Sat, 02 Jun 2012 15:35:10 -0400, Terrell Russell
<terrellrussell at gmail.com> wrote :
> > 
> > On 6/2/12 3:12 PM, Saint Germain wrote:
> > One interesting point is that I started with a 1-out-of-2 scheme
> > (the other storage node was local on my computer) and that Guido's
> > storage node was unavailable.
> > So when I copied a file on the "grid", it was pretty quick.
> > 
> > So that leads to one interesting question. Next time I will connect
> > with Guido's node available, will it upload the files I have
> > uploaded on my local storage node ?
> > 
> > If that is the case, I can have quick read/write on the local
> > node ? ;-)
> > 
> 
> As I understand the current state of things...
> 
> As long as the file is 'happy', then no, by default, there will be no
> more uploading/downloading of the shares of that file around to the
> other node(s).
> 
> What you're looking for is something to handle 'rebalancing' and
> perhaps 'repair'.
> 
> There are a few related tickets, but the first couple you should
> probably watch are #699 [1] and #543 [2].  Many others are listed
> under the keyword 'repair' [3] on Trac.
> 
> This is not implemented in a release yet, but is also related to the
> ongoing (and highly anticipated) accounting work being done by Brian
> Warner.
> 

Back again on the mailing-list !

Thank you for your explanation, now I understand the 'happy' parameter.
I suppose that if we allow upload when x server are available with
x < H, then there will be indeed happy and unhappy files.

With automatic rebalancing, the behavior will become more similar to
Dropbox !

Regards,