Cisco Cisco TelePresence Management Suite (TMS) Version 15
Deploying a hot standby
Cisco TMS Redundancy Deployment Guide
Page 16 of 27
Setting up the secondary Cisco TMS server
1. Check that the operating system including service pack level on tms02 is exactly the same as on tms01.
2. Check that the servers are both configured with the same time zone; failure to do this will mean that the
start and end times of scheduled conferences are incorrect in the case of a switchover.
3. Run the Cisco TMS installer on tms02:
a. Choose the Custom installation mode and enter the IP address of the external SQL server when
prompted.
b. Install to the same directory as on tms01 and use the same log directory as on tms01. This is important
because the log directory path is stored as an Environment Variable in Windows and not in the SQL
database.
database.
c. If HTTPS was enabled during installation on tms01, use the same certificate used on tms01.
4. After the server has rebooted, log in to the Cisco TMS web application to verify that it works correctly.
5. On tms02 go to
Administrative Tools > Configuration > Network Settings > Advanced Network
Settings for Systems on Internal LAN
. Make sure the IP address is tms01 (10.0.0.10) and the host
name is tms.example.com as the installer could have changed these values.
6. Open the Services Management Console on tms02:
l
Stop all the Cisco TMS services - they all have names starting with TMS.
l
Stop the Internet Information Services (IIS) service called World Wide Web Publishing Service.
l
Set the Startup Type of the IIS and TMS services to “Manual”.
Tms02 is now ready to act as a warm spare in the case of a failure on tms01.
Note that in
Administrative Tools > Server Maintenance > TMS Service Status
you will see the services
for both servers. Click on Clear List to remove the stopped services on tms02 from the list.
Synchronizing local files
Some customizable files used by Cisco TMS are stored in the Windows server's local file system rather than
in the tmsng database. The folders these files are stored in must be kept synchronized between the two
nodes. See
in the tmsng database. The folders these files are stored in must be kept synchronized between the two
nodes. See
for a full list of the folders that must be
synchronized.
Use your preferred method of synchronizing the folders. One way to do this is:
1. Create a shell script that uses xcopy/robocopy to copy files to the corresponding folders on tms02.
2. Use the Windows Task Scheduler on tms01 to run the script each hour.
If you swap the two servers in the event of a failure on the primary server, change the synchronization
mechanism you set up for keeping the folders on tms01 and tms02 in synch so that it now synchronizes from
tms02 to tms01.
mechanism you set up for keeping the folders on tms01 and tms02 in synch so that it now synchronizes from
tms02 to tms01.
Upgrading Cisco TMS
You must keep the Cisco TMS software versions on the primary and secondary servers consistent. After
upgrading the primary server, you must upgrade the secondary server as soon as possible. If the primary
server fails while the secondary server is on an older software version, you will not be able to swap the
servers until you have upgraded the secondary server to the newer Cisco TMS software version.
upgrading the primary server, you must upgrade the secondary server as soon as possible. If the primary
server fails while the secondary server is on an older software version, you will not be able to swap the
servers until you have upgraded the secondary server to the newer Cisco TMS software version.