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

Re: Stone-dead repository

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-02-20 13:32:11 CET

> Our server configuration is as follows:
> - RedHat Linux 9.3
> - Subversion-0.37.0-1
> - subversion-tools-0.37.0-1
> - apr-0.9.5-0.2
> - neon-0.24.4-1
> - httpd-2.0.48-3
> - 256MB RAM

What version of db4? If it's 4.1, then you need to seriously consider getting
Subversion compiled with db 4.2. I've seen more and more problems with 4.1
popping up on the list.

> Interestingly enough, when we retried the documentation commit after
> restoring the backup, the commit succeeded, so the problem doesn't appear
> to be a consistent one.

Well, it would be consistent with the db 4.1 reports I've been seeing on the
list. The problems seem to happen somewhat randomly, and there have been
several instances where everything ran fine, until months down the road when
db 4.1 finally did something strange and corrupted the repository. If have
4.1, spend sometime and recompile everything using 4.2. You won't regret it.

> Any pointers/recommendations for a good incremental backup strategy will be
> most appreciated.

I'm afraid that I can't help you much here. The repositories I have are all
small enough that I dump them every night, put them into a tarball, and both
backed up on tape and shipped to another server. Someone else on this list
might have a better suggestion for doing this with larger projects.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 20 13:34:10 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.