[cvsnt] Multiple CVSNT Instances

Trevor Leybourne trevor.leybourne at aderant.com
Mon Oct 31 23:54:15 GMT 2005

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

Hey Bo,

We are doing (almost) exactly what you are indicating below. I just re-read 
and noticied your point on only CHANGED files. I'll go and talk to our IT 

The problem is the number of files. Currently we have over 175,000 files 
spread of 12,000 folders in our 15 repositories and we've only been going in 
CVS for a few months. The copy is taking around 1 hour but has been as long 
as 2.5 hours and we are copying from one partition to another on the SAN 
which is on a 1GB fibre channel card.

Thanks for the feedback. Appreciate it.


"Bo Berglund" <Bo.Berglund at system3r.se> wrote in message 
news:mailman.4.1130761965.8612.cvsnt at cvsnt.org...
I don't think it is easily done to tweak CVSNT into becoming a multiple
server system.
However, I don't feel it is even necessary in reality.

What you could do instead is this:

1. Set up a scheduled task for refreshing a "shadow" repository.

2. The task should run a command file (batch) which contains an xcopy

3. The xcopy command should copy the entire repository tree over to a
   different part of the same disk or to a separate disk on the server
   PC. Note: don't copy over the network because you will not get the
   speed you want.

4. The xcopy parameters should be set to only copy *changed* files (where
   the archive attribute has been set, and reset the attribute afterwards)

5. Before and after the xcopy you should put a *net stop cvs' and 'net start 
   command to ensure that no file changes happen during your xcopy operation
   and that no files are locked when you want to copy them.

6. Direct your nightly backup system to back up the shadow repository 
   of the real one.

The first time around you will have to copy everything of course and this 
probably be done with manual monitoring. It will take longer than the 
refresh because there simply are more files to handle. Once done you only 
to handle changed files in teh future.

I have a system similar to this in place on one of my servers and it works
real good.


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Trevor Leybourne
Sent: den 31 oktober 2005 00:01
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] Multiple CVSNT Instances

Is it possible to run multiple CVSNT instances on the same server with each
instance managing a different set of Repositories?

We have a single multiprocessor server running a single CVSNT instance which
manages about 15 separate repositories. The issue we have is our IT
department want to ensure a clean backup is taken each night and shut down
CVSNT to perform the backup which currently takes between 1 and 2 hours.
Since we are a global development shop, this isn't very helpful to our

If we could run say 5 separate CVSNT instances (and I assume 5 LockServer
instances as well?), each one managing separate sets of repositories, we
could setup the backup processes to only shutdown part of the server, backup
those repositories and restart. It would bring each individual repositorys'
backup time down to 10-15 minutes max (much more manageable) and allow us to
stagger when different repositories are backed up (ie: the ones most used by
the US for example would backup during US nightime while the NZ/AU
repositories would backup during NZ/AU nighttime).

Any ideas or thoughts?


cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs 

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook