[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: Pejvan BEIGUI <pejvan_at_online.fr>
Date: 2004-07-18 19:49:30 CEST

John Szakmeister wrote:

> On Friday 16 July 2004 13:14, Pejvan BEIGUI wrote:
> [snip]
>>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.
> -John

You're absolutely right about all this. I have indeed a back-up of the
last two days, and I felt really safe with this. The only thing which
went wrong is that I haven't used svn for a few weeks and don't know why
the base got corrupt and hence I didn't notice it and back-uped the
corrupt DB. I guess that I'll add a daily incremental dump to another
backup procedure.

Anyway, I'll keep on using SVN since I find it being a lot easier to use
than CVS and it's also really more versatile :-)


Pejvan BEIGUI                                     pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.

Received on Sun Jul 18 19:50:15 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.