[volunteergrid2-l] New Member

[Shawn Willden]

Ah, okay.

I wouldn't bother backing up the Tahoe server at all.  The whole point of
Tahoe-LAFS is that the grid is distributed and replicated for safety, so
loss of any one node doesn't result in the loss of any data.  It's expected
that nodes will occasionally die, and that's okay; everyone should be
running the repair process periodically, and that will repopulate any
missing shares.  So if your node dies, just stand a new, empty, one up in
its place.

There is one thing you should make sure you keep in order to have access to
your data, though.  That's the root DIRCAP for your backups.  With that
string plus access to a node on the grid (even a newly-added node), you
should be able to retrieve all of your data.

On Tue, Feb 14, 2012 at 12:07 PM, Johannes Nix <Johannes.Nix at gmx.net> wrote:

> Hello Shawn,
> >
> > > BTW, can you give me some information how a safe and efficient backup
>
> > I think most (all?) of us are using "tahoe backup".
>
> Oh, maybe I wasn't clear enough with my quesstion.
> Yes, I think "tahoe backup" is a good solution for saving private precious
> bits to the grid.
>
> What I was wondering, however, was what I need to consider when I back up
> the tahoe server. As far as I understand, everything I need to recover is
> under $BASEDIR/storage and can be saved by incremental copies, right?
>
> Also, restoring 500 G can be a lengthy process, and I thought in the "cp
> -al && rsync -raH" variant because that basically leaves a ready-to-go copy
> for a replacement server. Correct so?
>
> Johannes
> _______________________________________________
> volunteergrid2-l mailing list
> volunteergrid2-l at tahoe-lafs.org
> http://tahoe-lafs.org/cgi-bin/mailman/listinfo/volunteergrid2-l
> http://bigpig.org/twiki/bin/view/Main/WebHome
>



-- 
Shawn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/cgi-bin/mailman/private/volunteergrid2-l/attachments/20120214/c77c17e4/attachment.html>