[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Hot backup changes

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-08-22 20:47:18 CEST

On Thu, Aug 22, 2002 at 06:29:43PM +0200, Benjamin Pflugmann wrote:
> Well, that presumes that you cannot make (reasonably) an incremental
> copy of the binary, what I do not know.

Yup. And that is where Blair got misdirected :-)

Just copy off the BerkeleyDB 'log' files, and you're totally set. Those can
be used to rebuild the entire database (through what tool, I dunno). As a
new log file becomes "complete" (detected via db_archive?), then you *move*
it outta your repository and to your backup area (the repos doesn't need it
any more, so it can be moved/deleted).

Really... Berkeley DB probably has instructions for all this.

[ I still support the notion of layering backup solutions on top of SVN
  itself, but I don't consider it entirely SVN's problem ]


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 20:43:03 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.