Moving TMS from physical server to VM with external SQL server

[Jens Didriksen]

What we have:

TMS 13.2 with TMSPE running on physical Windows 2003 Enterprise server with 2005 SQL server.

TMS application, tmsng and TMSPE all located on the same server.

What we wanted to do:

Move TMS 13.2 with TMSPE to 2008 r2 VM with tmsng located on separate (external) VM 2008 SQL server.

First attempt; both physcial and TMS VM servers with same hostname, different IP addresses.

(Physical server removed from domain after copying tmsng db and taken off line - then changed host name on TMS VM server ).

TMS 13.2 and TMSPE installed without a hitch on the VM, we then copied the existing tmsng db from the physical server to the 2008 SQL VM server.

All looked good, except we could not clear any of the TMS tickets telling us the various TMS services were not running, this despite stopping and restaring all TMS services a number of times.

TMPSE diagnostics showed all green, but the VCS-C told us a different story; with all connections; users, phone books and devices, failing with a http 400 error.

At that stage our window of opportunity was closing rapidly so we had to roll it back and bring the old, physcial server back on line.

During testing we used different host names for the physical and the MV servers, but we found TMS2 raising tickets telling us the various TMS services were not running on TMS1, hence we thought we'd try with identical host names for both TMS1 and TMS2.

Are there some dependencies we missed?

Any advice on how to best achieve this would be very much appreciated.

cheers

/jens

[Magnus Ohm · Accepted solution]

Hi

Ive seen this issue many times before and its basically generating tickets because it has a double set of services listed in under TMS Server Maintenance (At the bottom), as the list follows the TMSNG db when you move it, it will show that it has for example 1 TMS Live Service running and one TMS Live service shutdown where the second one is generating this ticket. Just click the clear list to fix the problem.

In regards to the TMSPE, did you move the TMSPE db as well over to the new server or did you keep it running at the old one?

Was all the configurations correct in terms of username / domain etc in the provisioning settings?

Best Regards

Magnus Ohm

[Jens Didriksen]

Aha!

That explains why these tickets kept on popping up within seconds of deleting them - thanks Magnus

As for the TMSPE, that was a fresh install on the VM, username/domain etc was all correct.

We'll give it another go during our next maintenance window.

Is one method of moving the tmsng db across more correct than the other; - as in copying across vs detaching from the old, then attaching to the new?

cheers jens

[Magnus Ohm]

Detaching the database and copy across the servers and attach or take a backup, copy across and restore it at the other server. The result is the same. Or if you have an external db, just change the db connection settings in TMS to connect to

The same db as the old one and shut the old tms server down.

Its just that some information from the old one will follow and might give some unexpected results. But from what i have experienced there is not too many devastating problems you can encounter.

/Magnus

Sent from Cisco Technical Support iPhone App

[Jens Didriksen]

Thanks Magnus, as always; very much appreciated.

/jens