Re: Hot to restore repo from hot-backup.py

Eric Gillespie <epg@pretzelnet.org> writes:

>
> /usr/local/BerkeleyDB.4.0/bin/db_recover -ve -h ${repo}/db

We've already got this information in the Handbook (in the "Repository
Maintenance" section), although it only mentions running this command
to unwedge a "frozen" repository.

I'm surprised at your use-case though; here we have a situation where
the repository isn't wedged at all, yet db_recover reveals unplayed
transactions? How is that possible?

To do a "hot backup" of a db environment, all you need to do is
1. copy the whole db/ area somewhere, and then 2. re-copy the logfiles
out again in a certain order. Does this reveal some kind of
explanation?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 17 23:24:47 2002