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

RE: RE: AW: Companies Using Subversion

From: Crucius, Wesley <WCrucius_at_sandc.com>
Date: 2004-05-05 18:57:35 CEST

Can you tell us more about your VSS to SVN conversion tool, and your
replication scheme?


-----Original Message-----
From: Stuart Robertson [mailto:dogmatix@absolutesys.com]
Sent: Wednesday, May 05, 2004 4:25 AM
To: users@subversion.tigris.org
Subject: RE: AW: Companies Using Subversion


I introduced SVN to Absolute Systems Inc. (www.absolutesys.com) where I
work about a year ago, and for about 8 months we ran internal SVN
pilots, played around to gain experience and trust, etc.

In the last 4 months we have migrated all of our internal product source
repositories from Visual Source-Safe to SVN using an internally-written
VSS-to-SVN migration tool.

Our largest SVN repository is now 3.7GB and currently has 68806
revisions. We are running SVN 1.0.1 + Apache 2.0.48 on Linux.

We now have a master-slave repository setup where all commits are made
to the master svn server, and the slave server regularly (currently
every 5
minutes) synchronises its repositories with the master's repositories,
so we have a fairly fault-tolerant system.

Recently we had a substantial hardware failure on the master server, and
it was a simple matter of changing hostname and IP-address on the slave
and all of our developers were able to continue working.

We are somewhat paranoid about data-loss, so we make complete backups
daily and we store the last 2 weeks' complete backups offsite. Having
said that, however, to date we have had no problems that have required
us to ever rollback a day, or that have resulted in data loss.

SVN is a superb piece of work, and it is a *huge* step forward from VSS.
To put things in perspective... previously we had 26 VSS databases for
one product, primarily because of problems with VSS when the
repositories grow large. As you can imagine, trying to manage product
releases across so many repositories was really painful.

Now, with SVN, *all* of the artifacts for that same product are in a
single repository, meaning that with a few cheap copy operations all of
the sources that make up a given release can be grouped together.

I would suggest that you first pilot SVN internally, before jumping in
the deep end. We learned a lot during our piloting that allowed us to
better understand what we were getting ourselves into.

Hope this helps.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 5 18:58:19 2004

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.