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

Re: how does tigris do server updates?

From: Blair Zajac <blair_at_orcaware.com>
Date: 2007-07-21 21:33:59 CEST

Blair Zajac wrote:
> Brian Krusic wrote:
>> Hi Mark,
>> While u r correct about serving dbs regardless version as thats what
>> we do on some of our repos now, there are benefits to upgrading so I
>> disagree with you.
>> A repo we had in 1.2.3 was 50GB at the time. We converted to 1.4 and
>> it shrank to 38GB.
>> So yes, we do need to convert.
>> With offices in geographically diverse regions, the leaner and meaner
>> our dbs are, the better.
> Shrinking the repository size won't have an impact on the network
> traffic to your clients, even if they are geographically dispersed. So
> while it's nice to dump and load, it's not necessary.

Some more thoughts. Saving 12 Gbytes in repository size is nice.

What I would do is

1) Dump and load into a fresh repository while the older repository is
still live.
2) If the old repository has had commits, then dump and load those in to
the new repository.
3) Copy any hook scripts from the old repository into the new repository.
4) Shut down the svn server.
5) Perform step 2 once more to pick up any last commits.
6) Rename the old repository and rename the new repository into its place.
7) Start the svn server.

You're looking at a couple of minutes of downtime here.


Blair Zajac, Ph.D.
Subversion training, consulting and support
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 21 21:33:17 2007

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.