svnadmin recover, backup and recovery strategies

Here's my setup:

I'm running RH Linux 7.3 with Subversion, using the following:

db4-4.0.14-0.4.i386.rpm
db4-devel-4.0.14-0.4.i386.rpm
db4-utils-4.0.14-0.4.i386.rpm
neon-0.24.4-1.i386.rpm
neon-devel-0.24.4-1.i386.rpm
subversion-1.0.1-1.rh7x.i386.rpm
subversion-devel-1.0.1-1.rh7x.i386.rpm
subversion-python-1.0.1-1.rh7x.i386.rpm
subversion-server-1.0.1-1.rh7x.i386.rpm
subversion-tools-1.0.1-1.rh7x.i386.rpm

Today we had some tense moments while the DB appeared inaccessible.
Following the instructions in the manual, I stopped Apache and ran svnadmin
recover.

We apparently had a huge import last night, but it appeared to work. Yet
this morning, all of a sudden, people were having problems accessing. We
had a second incident around midday where someone said he/she was checking
out "empty directories." I have now run a second svnadmin recover, and
everything appears OK now, but I'm concerned that I may continue to have
problems.

Any suggestions? Should we upgrade?

***********************************************************
Frances H. Butler

Computing Specialist
BWXT Y-12 L.L.C.
Technical Computing/Enabling Technologies
Oak Ridge, TN 37830

Phone: (865) 574-3694
E-Mail: butlerfh@y12.doe.gov

***********************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 9 23:10:17 2004