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

Eric Gillespie <epg@pretzelnet.org> writes:

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

No, it just documents your example of 'db_recover' as a way of making
Berkeley DB replay transactions; but the Handbook says that this is
only necessary when the repository locks up... because, well, that's
the only time we've ever had to use it!

But your use-case opens a whole new set of questions...

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

It means run 'db_archive -l', examine the list of logfiles it prints
out, and then copy them out in that order.

> I asked on the #svn channel how to restore, and no one knew.

This is what puzzles me. There's no such thing as "how to restore" a
backup; you just start using it. No special knowledge required. Or
so I *thought*

But it seems that your backup had unplayed transactions in it, which I
don't get. Can someone more knowledgable explain? Perhaps
Mr. Bostic? :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 18 00:38:18 2002