You have two options for performing a recovery, both easy.  First method,
"svnadmin recover REPO", second method "db4.X_recover -h REPO".

I've had to do it a dozen times for various reasons, all of which were my
fault.

The *BEST* way to back up an SVN repo is to do a dump.  It's a complete
snapshot of the repo and its history.  However, failing that, revisional
dumps work great, and with a small shell script, you can completely automate
the process of rebuilding the repo if you should ever have to do that.  My
greatest recommendation...get RAID.


On 1/18/06, John De Villiers <bbj@plz.co.za> wrote:
>
> On Wed, 2006-01-18 at 13:47, Gerhard Fiedler wrote:
> > If you have a second machine with enough disk space, why don't you just
> > copy the repositories (the directory trees with all the RCS *,v files)
> > nightly? This gives you the same safety as your nightly updates, plus
> all
> > revision history, tags and commit comments. In case something bad
> happens
> > to one of your repositories, just copy the backed up RCS files back and
> > you're back in business.
> >
> > Gerhard
> Because thats the way i chose to do it.
> Also, svn doesnt use rcs *,v files. It uses a berkeley (sp?) database,
> and i havent tried recovering a BDb yet. The correct way to back it up
> would be to shut svn down first, and then copy the files.
>
> I dont know BDb that well ( at all ) so i steered clear of it affecting
> a recovery.
>
>
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>



--


Shawn Wilton (b9 Systems)
http://black9.com
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist