On 9 Jun 2003 cmpilato@collab.net wrote:
> Without seeing exactly what you did and in what order you did those
> things, I'm not able to really poke a guess at what ails you. All I can
> say is that the folks at Sleepycat recommend a particular algorithm for
> making hot backups of Berkeley DB environments which is guaranteed to
> not screw stuff up, and it is that algorithm which hot-backup.py
> follows.
You misunderstand. This is not a complaint or request for help. I just
wondered why, if the files created are temporary, that the repository
appears to have changed even after the transaction (eg. `svn co ...') was
completed. Clearly this is no problem as such.
> If we can agree on two things,
>
> (1) that the hot-backup.py algorithm is the only one which
> guarantees a usable backup repository, and
> (2) that rsync will faithfully copy byte-for-byte filesystem
> segments across a network,
>
> then I think we have a recipe for scratching your itch. To use
> another non-Sleepycat-sanctioned backup method on a live repository
> takes us into the realm of academic discussion -- not my favorite
> flavor. :-)
Ok. I quite understand if you don't want to have an academic discussion.
I've guess I've spent too long in universities. :-)
Faheem.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 10 01:19:40 2003