TANDBERG TMS SERVER REDUNDANCY - CONFIGURATION GUIDE 13.0 Configuration Manual - page 16
Cisco Redundancy Models for Cisco TMS
Cisco TMS redundancy configuration and overview
Page 16 of 32
Multiple Servers, Manual Cutover
While the previous sections have covered redundancy for the SQL database, they do not provide
solutions for quick fail-over for the Cisco TMS Server itself which hosts the Cisco TMS website and the
Cisco TMS Windows Services. To speed recovery time for the Cisco TMS server, you can install
additional ‘warm spares’ of the Cisco TMS server. In this model, there are multiple Cisco TMS servers,
all pointed to the same separate SQL server, but only one Cisco TMS Server is considered the active
server. The secondary machines are configured, but are disabled to remain inactive. Then, if the
primary Cisco TMS server fails, a
secondary Cisco TMS server can
quickly be activated, allowing Cisco
TMS to be available while the primary
server is being worked on. The SQL
database can be redundant as well if
deployed using a SQL Server Cluster.
In this scenario you have multiple
servers on different addresses and
but only one Cisco TMS server can
actively receive events and activity
from users. Theoretically while
individual devices and users could be
directed to different Cisco TMS
servers, this will lead to erroneous
warnings in Cisco TMS for device
configurations. In addition, the Cisco
TMS Services installed on the
secondary machines will be active
and actually process events and call
activity.
Note: To prevent confusion and assist
in troubleshooting, Cisco
TelePresence recommends you not
run the Cisco TMS services on the
secondary servers while they are not
the active Cisco TMS server.
This model can be thought of as a
‘manual’ fail-over between multiple
Cisco TMS servers to reduce
downtime, but at the added cost of
having additional stand-by servers.
Recovery Methods
Cisco TMS Server Failure.
•
Repair the existing server and bring it back online or,
•
Free up the IP address normally used by Cisco TMS by changing the primary server’s IP
address to an alternative IP address. Reconfigure one of the secondary Cisco TMS servers
to be the IP Address and DNS hostname of the primary Cisco TMS server which is no longer
online. Activate the Cisco TMS Services (all services whose names start with Cisco TMS and
the WWWPublishingService). This machine is now the primary Cisco TMS server.
Alternatively: If managing only systems that support DNS hostnames for management
settings, you can simply update the DNS hostname record to point to the new server’s IP
address, update the Cisco TMS Server Local IPv4 Address (and IPv6 if in use) configuration
value and start all services on the new Cisco TMS server.
SQL Server Failure – The SQL Cluster will automatically handle the fail-over of assigning the
Virtual SQL Server resources to another node in the cluster. This happens transparently to Cisco
TMS. Please refer to the Microsoft SQL Server documentation for information on restoring a node
in a SQL Cluster.
Error! Objects cannot be created from editing field codes.
Figure 1 Multiple Stand-by Server Illustration