[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: backing up a repository over a network

From: Faheem Mitha <faheem_at_email.unc.edu>
Date: 2003-06-09 21:37:38 CEST

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?

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.

Repository -> Local Backup (using hot-backup.py) -> Remote (using rsync)

Is this what you meant?

But the problem that rsync is svn unaware is still the same. Would it
be very difficult to modify hot-backup.py to work over a network?


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:38:41 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.