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 email@example.com.
On Fri, 21 Nov 2008 11:55:22 -0600, "Bryan" <broberts at atlas-mts.com> wrote: >"Bo Berglund" <bo.berglund at telia.com> wrote in message >news:0dqdi45e65q4t9s9d787qn3aithcc123j6 at 4ax.com... >> On Fri, 21 Nov 2008 10:05:01 -0600, "Bryan" <broberts at atlas-mts.com> >> wrote: >> >>>Does anyone have a process to migrate the CVSNT application from one dying >>>MS 2003 server to another 2003 server. >>> >>>Much appreciated. >>> >> >> How about: >> - Arrange the disks the same way on the new server as on the old one >> - Install CVSNT on the new server, then stop the CVSNT service. >> - Install other software that you know you use with CVSNT (like >> CVSMailer for example) to the same locations as on the old server. >> - Stop the CVSNT service on the dying server >> - Copy the repositories from old to new server over the network to the >> same locations on the new as on the old server >> - Export the registry settings for CVSNT on the old PC to a reg file >> - Import the registry settings on the new server via the reg file >> - Now disconnect the old server from the network >> - Then rename the new server to the same name as the old one (restart >> needed) >> - Make sure CVSNT service is started >> >> - Make tests from clients that they have a connection like they used >> to. >> >> Done. >> >> What this does is replicating the repository into the same structure >> as on the old one, which makes the CVSNT settings work also on the new >> server when you import them via the reg file. This way the new server >> will use the same conbfiguration as the old server. >> >> And by installing support software like CVSMailer to the same location >> on the new server as on the old you make sure that the scripts in >> CVSROOT will still run as before. >> >> Finally by renaming the server to the old name the clients will not >> notice any difference, their sandboxes will continue to work. >> >> Note that you need to shut down the old CVSNT service (and never bring >> it up again) before copying the repository files so that there will >> not be an intermediate commit or other action in the repository while >> you migrate. >> >Changing the name of the server is not an option. How much do that change >the procedure? > If you cannot change the server name then you can modify the DNS settings of your network so that the old server name is kept but pointing to the same IP address as the new server. The reason for this exercise is to keep all of the developer's sandboxes functional against the new server. Ideally they should not have to do anything to keep their workflow, just observe the downtime during migration. Next possibility is to have every developer with checked out files modify his %systemroot%\system32\drivers\etc\hosts file and add an entry with the old server's name and the new server's IP address. This masquerades the new server as the old as seen from the clients. If also this is not possible then every single developer will have to go over his checked out file sets (sandbox) and either delete them and check out fresh from the new server or alternatively run a macro or similar to modify every single Root file throughout his data to reflect the new server name. The WinCvs front-end has such a macro that can be activated on a directory level and works recursively down.... It all boils down to convenience of the users. If you are the only user then the trick to change the Root file contents is possibly the best bet. -- /Bo (Bo Berglund, developer in Sweden)