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

Ben Collins-Sussman <sussman@collab.net> writes:

> 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.

It already documents how to restore from the backup? I just looked
and couldn't find that anywhere.

> 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?

No idea. Bill Tutt knew there were unplayed transactions in the
backup already; he's the one who told me that. That's when i
decided to try db_recover.

> 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?

Don't ask me. What does "re-copy the logfiles in a certain order"
mean? I asked on the #svn channel how to restore, and no one knew.
Bill Tutt mentioned replaying log files, but he didn't know details.
So i poked around the db documentation and figured i'd give the
db_recover command a whirl. It worked.

--
Eric Gillespie <*> epg@pretzelnet.org

Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett

---------------------------------------------------------------------
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:44:44 2002