[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 22:42:08 CEST

On 9 Jun 2003 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.

Good heavens. If every checkout etc. is logged with the database, then it
must grow enormous over time. And I run `svn st -u' and `svn up' all the
time. If these change the repository, then that might account for the
problems I've been having. I don't see why it is necessary to log all this
activity, though.

I see the Subversion Book refers to logs, but I thought they were logs of
commits. I didn't realise it was logging all this other stuff.


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:43:07 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.