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

Re: Faster SVN Status

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Mon, 07 Jan 2008 09:34:12 -0500

Niel De Clerk wrote:
> Thanks, I'll go for option 1.
> Relocating the repository is a simple as making a hot copy to the new
> location and pointing the service to the new location, right?

You don't need to hotcopy if you know that no transactions are taking
place (see next answer). And ordinary recursive file copy is fine. If
you were anywhere but Windows, I would recommend using rsync (since you
could rsync once while the repo was still active then a second time
after the service was disabled). You may find a native rsync for
Windows (but you probably shouldn't use Cygwin, since that can introduce
odd file permission issues)

> Is there an easy way to ensure no transactions take place during such a
> transfer?

Shut down the service on the public machine; no one is going to die if
the repo is offline for the time it takes to copy the files.

> Will locks etc remain in place, or should all clients first
> commit their last changes and release their locks?

If you copy the entire repository directory structure (or better yet,
zip it up and copy for back up purpose), you should notice nothing
except a speed improvement.

NOTE: I have never personally done this operation; I always install the
repo local to the service.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-07 15:34:46 CET

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

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