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

Re: Recover after HD crash (SVN with FSFS backend)

From: Dirk Schenkewitz <schenkewitz_at_docomolab-euro.com>
Date: 2006-05-09 14:03:56 CEST

On Tuesday, 9. May 2006 00:54, Giovanni Bajo wrote:
> Ryan Schmidt <subversion-2006q2@ryandesign.com> wrote:
> >> I'm running a SVN 1.3.1 server (under Apache) with FSFS backend.
> >> After a HD
> >> crash, we recovered the server status as 3-4 days before the crash.
> >> Thus, we've
> >> lost the last 100 revisions in the server. We didn't lose any
> >> actual data
> >> though, since we have many working copies of the various projects
> >> updated to
> >> the last version before the crash.
> >>
> >> The question is: is there a way to extract these data from the
> >> working copies
> >> and put it back into the server, in a way *not* to invalidate all
> >> the working
> >> copies?
> >
> > I don't think so.
> After much experimentation, I gave up and had to ask my users to destroy their
> working copy.
> This is however a very critical point. Nowhere it is documented that Subversion
> needs to be backed up *every single* revision, or you are going to lose all
> your working copies in case of HD crashes. I guess this should be spelled out
> very clearly in the SVN book and documentation. In fact, I'm trying to setup a
> backup system as post-commit hook, as doing it daily or weekly is basically
> useless.

Could you shortly describe what you tried?

I would do the following:
A) copy a WC to another name, perhaps 2 times while you're at it. Then do an
svn revert to switch back to what should be the latest checked in version if the
server would be fine. Then try to checkin. If that does not work:
B) checkout the latest version from the server to a NEW directory. Copy
everything from the just 'revert'ed WC into it. Check in. This must work.
C) at last copy everything from the unreverted copy ontop of it. Check in.

Altogether, you'll loose some history, and the lastest revnums are different,
but the latest that was checked in (the one that becomes actual after a 'revert')
should be 'restorable' and the next one (the latest state of a WC, not yet
checked in) also.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 9 14:03:29 2006

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.