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

SVN server crash, restore from backup gives problems

From: Peter Mounce <pete_at_x-rm.com>
Date: 2004-08-27 18:29:15 CEST

Hi

We just had our fileserver's hard drive crash - it runs Windows 2k
sp4, with SVN 1.06 and Apache-for-Windows. This took our SVN
repositories (we use one repo per project, for reference) with it; now
we're restoring them from our tape backups. It was a great Friday.

Anyway, one of the repos is giving us problems. When we restore our
most recent full backup, we can access it fine - this brings us to
last Friday, so none of this week's commits are present.

When we then restore incremental backups over that, we get the
following error when attempting to access the repo via a browser:

<D:error>
<C:error/>
-
        <m:human-readable errcode="160029">
                          Berkeley DB error while checkpointing after Berkeley DB transaction
                          for filesystem F:\svnrepo/dls/db: Invalid argument
</m:human-readable>
</D:error>

(Apologies for formatting)

Our daily diff seems to have all of the files, and they verify as ok
in the backup logs.

We'd quite like to know how to proceed... Anyone have any useful
advice, please?

Luckily, we have a most-recent working copy (which we have now
panic-backed-up to a CD...) of the project that is stored in the
troublesome repo, so I guess in theory we could commit that back to
last Friday's image of the repo - but we'd like to restore as much
history as possible.

Thanks in advance!

-- 
Regards,
Peter Mounce  ( mailto:pete@x-rm.com )
Software Developer    http://www.x-rm.com - X-RM Ltd, Winchester
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 27 18:36:08 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.