Re: backing up a repository over a network

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

> On 9 Jun 2003 cmpilato@collab.net wrote:
>
> > Faheem Mitha <faheem@email.unc.edu> writes:
> >
> > > In any case, I noticed there is a subversion script (hot-backup.py) which
> > > does a repository backup that is intelligent, so less likely to give a
> > > broken result. However, it seems designed for local use, and not for
> > > networking.
> >
> > Considered using a combination of hot-backup.py and rsync? Make a hot
> > backup locally, and then rsync it to another machine.
>
> I don't follow. I already have a repository locally. As I understand it
> (correct me if I am wrong) hot backup just clones my repository locally.
> So what is the advantage over directly rsyncing my (original)
> repository?

Well ... oh. You already figured it out. :-)

> Oh, I suppose that protects against the possibility that I am writing to
> the repository at the same time. So it would remove one possible source of
> error. Ie.

Yep, that's it.

> Repository -> Local Backup (using hot-backup.py) -> Remote (using rsync)
>
> Is this what you meant?

Exactly.

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

> Would it be very difficult to modify hot-backup.py to work over a
> network?

I dunno. Care to give it a shot? :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 9 21:52:37 2003