[cvsnt] Any migration caveats between CVSNT versions?

Jim Hyslop jimh at view22.com
Fri Oct 20 18:59:56 BST 2006

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.

Paul Bennett wrote:
> The rest of your reply caused mine eyes to glazeth over a 
> tiny bit. I'm a sysadmin, not a CVSNT admin (nor even a cvs 
> user).

Non-sequitor. Being a sysadmin requires you to have knowledge of all the
systems you are administering.

Let me put it this way: if I applied to work with you, and said I was a
sysadmin but I don't know anything about MS Exchange, DNS and WINS
servers, or IIS, how hard would you laugh before chucking my resume?

CVSNT is no different. It is one of the server applications you are
required to administer, therefore you should be familiar with the terms
and basic operations of version management.

OK, now that I've got that out of the way... :-)

I usually try to use a DNS alias for the repository server. That
simplifies future migrations: just set up the new machine, test it out,
and when you've got all green lights it's a simple matter of switching a
couple of DNS entries. Completely transparent to the users. You must, of
course, make sure nobody modifies the repository between the time you
copy everything over and the time you make the DNS switch. The exact
steps you need to take to do this will depend on how large your
repository is, how many users there are, and how long you can have the
server off-line.

If you run into any difficulties, feel free to ask here.


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