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

Re: database corruption

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-07-17 13:49:50 CEST

On Friday 16 July 2004 13:14, Pejvan BEIGUI wrote:
> This BDB thinguy starts to frightening me. And I'm about to install svn
> for a whole team of developers, which frightens me even more now...
> Anyway, it's the right time to make a DVD-RW back-up I believe :-)
> Thanks again for your help.

You may want to consider strengthening your backup process here too.
Personally, I'm a bit paranoid when it comes to our source code, so all
of our repositories are hotcopied into a backup directory. I run
'svnadmin recover' on each repository, as well as 'svnadmin dump' on each
repo in the backup directory. Both the hotcopy and the dump are tarred
and backed up to tape. All of this is done nightly as part of a cron
job. This way, a maximum of one day may go by before I'm informed of any
corruption (although, I'm certain one of my fellow developers would
complain well before then :-). It may be overkill, but I feel
comfortable in that I never have to worry about a severe loss of data.

A more paranoid person would probably use the 'svnadmin dump
--incremental' in conjuction with a post-commit hook script to save off
commits during the day. Commit mails can also be useful in grabbing
those few remaining revisions to restore as well (which we employ as both
a method to restore missing revisions, and for code review). Note that
commit mails generally don't contain binary data, so if you have a lot of
that, 'svnadmin dump --incremental' is really the way to go.

I can't stress how important it is to have a good backup solution. I
sleep well at night knowing that our data is as safe as we can possibly
make it, and that all isn't lost if/when a catastrophic failure or
corruption occurs.

That being said, if you have a good backup solution in place, there is
nothing to fear. We've been using Subversion successfully since 0.17 and
haven't lost one revision of data. All of our developers love the tool,
and I love the fact that we can identify corruption before it gets to be
a real problem, unlike CVS.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 17 13:52:09 2004

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

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