Re: backing up a repository over a network

On 9 Jun 2003 cmpilato@collab.net wrote:

> Faheem Mitha <faheem@email.unc.edu> writes:

> > But the problem that rsync is svn unaware is still the same.
>
> I don't really understand the "svn unawareness" issue. Files are
> files, right? Binary data. Ones and zeros. Now, granted, if you
> move a Berkeley DB environment between some platforms, things'll be
> all busted up. That's why Berkeley provides its own db_dump and
> db_load utilities, to take care of endianness issues between
> platforms.
>
> But is there some other particular problem haunting you?

Well, in a nutshell, rsync *should* make a perfect copy of the repository,
which should Just Work. Sometimes, it doesn't. So I'm wondering why.

Now, it could be that by bad luck the repository is changing at the same
time as the backup is performed, and that could be all of the problem. I'm
not actually sure when the repository changes. I thought earlier it would
only change during commits (which I don't do that often), but as I wrote
earlier, this does not seem to be the case. Would anyone like to share
with me under what circumstances the repository would change (and why)
aside for commits?

Anyway, if that is the only problem, then what you suggest would solve it,
and I'll give it a try.

Oh, by the way, I'm copying from one Debian system to another, which are
identical in all significant respects from svn's point of view (yay
Debian) so platform differences should not be an issue.

> > Would it be very difficult to modify hot-backup.py to work over a
> > network?
>
> I dunno. Care to give it a shot? :-)

Don't know. It looks difficult, and I suck at programming.

                                                          Faheem.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 9 22:14:09 2003