[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: Jamin W. Collins <jcollins_at_asgardsrealm.net>
Date: 2003-06-09 22:35:18 CEST

On Mon, Jun 09, 2003 at 03:23:43PM -0500, cmpilato@collab.net wrote:
> Faheem Mitha <faheem@email.unc.edu> writes:
> > 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?
> We use Berkeley's transaction and log system for everything, and we
> use Subversion transactions as part of 'svn update'. So even updates
> (and therefore checkouts, status -u, diff, switch ...) are writing to
> the database.

This may be a little off topic for this thread, but how would one go
about maintaining several writable copies of the same SVN repository,
keeping them all in sync with each other? Is it even possible?

Jamin W. Collins
Remember, root always has a loaded gun.  Don't run around with it unless
you absolutely need it. -- Vineet Kumar
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:36:13 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.