[tahoe-dev] [tahoe-lafs] #780: Regularly snapshot dev infrastructure.

[tahoe-lafs]

#780: Regularly snapshot dev infrastructure.
--------------------------------------+-------------------------------------
 Reporter:  nejucomo                  |           Owner:  nejucomo 
     Type:  enhancement               |          Status:  new      
 Priority:  major                     |       Milestone:  undecided
Component:  dev-infrastructure        |         Version:  unknown  
 Keywords:  reliability organization  |   Launchpad_bug:           
--------------------------------------+-------------------------------------

Comment(by warner):

 FYI, I implemented a git-based backup of the allmydata.org/trac/tahoe
 environment on 01-Jul-2009. Every six hours, all non-ephemeral Trac state
 is copied into a directory and checked into a Git repository. Both zooko
 and I pull copies of this repo manually (whenever we think about it). The
 next step will be to automate the pull.

 While this approach doesn't use Tahoe, I think it's still pretty robust.
 Using Git gives us easy access to history as well as significant space
 savings (the SQL textdump of the trac.sqlite database diffs nicely, and
 all VCSes are designed to handle text diffs efficiently).

 While eating-your-own-dogfood has its merits, in the interests of safety
 it might make more sense to diversify the tools we use for backup
 purposes. Imagine the worst-case scenario: an omnipotent (but very
 selective) rogue AI manages to delete every copy of tahoe in the entire
 world! Now how do we use our clever tahoe-based backup scheme to recover a
 copy of tahoe? :-)

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/780#comment:1>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid