TANDBERG TMS SERVER REDUNDANCY - CONFIGURATION GUIDE 13.0 Configuration Manual - page 19
Cisco Redundancy Models for Cisco TMS
Cisco TMS redundancy configuration and overview
Page 19 of 32
Upgrading TMS
All Cisco TMS servers accessing the same database must be running the same Cisco TMS version.
When upgrading between Cisco TMS versions, there will be inconsistencies between different servers
as each is upgraded so extra steps are required when performing Cisco TMS upgrades or patches.
When performing a Cisco TMS upgrade, the following steps must be followed
Plan an upgrade during a time window when Cisco TMS can be made unavailable to users as
Cisco TMS will be unavailable during the duration of your upgrade.
On your primary Cisco TMS server, start the installer for the Cisco TMS upgrade as normal.
During this process, any updates to the SQL database will be performed.
Installation may require a reboot of the server. After the reboot, go into Services component of
Computer Management on the server, manually stop all services whose name starts with Cisco
TMS and the WWWPublishingService service.
Proceed to the next server, and start the installer for the Cisco TMS upgrade the same as you did
on the primary Cisco TMS server.
The installer will likely restart the Cisco TMS services and WWWPublishingService and may
require a reboot of the server. After the reboot, go into Services component of Computer
Management on the server, manually stop all services whose name starts with Cisco TMS and
the WWWPublishingSevice. The services may also be configured for automatic startup. Right-
click on each of these services and select Properties. On the General tab of each of the services
you stopped, set startup type to Manual.
After upgrading all Cisco TMS servers, log into the primary Cisco TMS’s Windows console and
restart all Cisco TMS services and WWWPublishingService. Secondary servers should all still
have their Cisco TMS and WWWPublishingService stopped and set to manual startup.
Log into the Cisco TMS website, go to Administrative Tools>Configuration>Network and
change the Cisco TMS Server IPv4 Address (Local): address to the IP address of the primary
Cisco TMS server. Your upgrade is now complete.
Upgrades will erase any changes to the IIS web configuration files, including the viewstate
machine key and method defined during installation. Repeat the viewstate key generation and
installation steps outlined in the Installation section on each of the upgraded web servers.
Model Summary
Immediate fail-over available.
Yes for SQL Server. No for Cisco TMS Server
Amount of data lost.
Call data during outage can be lost for some system types if Cisco TMS Server is down. If SQL
Server fails, SQL Cluster will fail-over and Cisco TMS will still be available. No data is lost when
the SQL Server fails over. Please be sure to read Section
0 Cisco TMS Redundancy limitations
and notes
for specific notes about processes during a server failure.
Time to restore service.
For clustered SQL servers, depending on configuration, normally on the order of seconds to
minutes. For a stand-alone SQL Server, it is dependant on time to repair the server or replace
with another server on the same IP address and perform a recovery. Estimate a few hours to a
day. For the Cisco TMS Server, it is dependant on time to repair the server or activate the ‘warm
standby’. Activating the warm stand-by can be done in just a few minutes.
Administrative Capabilities Required.
Low for Cisco TMS Server portion and stand-alone SQL server, very high if SQL Cluster must be
created
Cost.
Medium as you must now have a minimum of three servers