TANDBERG TMS SERVER REDUNDANCY - CONFIGURATION GUIDE 13.0 Configuration Manual - page 15
Cisco Redundancy Models for Cisco TMS
Cisco TMS redundancy configuration and overview
Page 15 of 32
install, select custom installation and point the installer at the existing SQL database. The
install will continue as normal and after installation your Cisco TMS server will be have the
configuration used prior to the failure. You should also restore customer specific Cisco TMS
data files (See Section
0 Customer specific TMS Files
) if the server is replaced.
SQL Server Failure – The SQL Cluster will automatically handle the fail-over of assigning the 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.
Installation
Configuring a Microsoft SQL Cluster is outside the scope of this document. Please refer to Microsoft’s
documentation for additional details
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
Prior to installing Cisco TMS, the SQL Cluster should be active and must have the Virtual SQL Server
installed and active that you wish to use for Cisco TMS. The Virtual SQL Server will have an instance
name and IP Address to reach the SQL server.
Once the Virtual SQL Server is configured, Cisco TMS can be installed on the separate Cisco TMS
server. The Cisco TMS installation program allows you to select an existing remote SQL server as part
of the custom installation. Select or enter the instance name or IP address of the Virtual SQL Server.
The installation program will fully handle the configuration of the database on the existing SQL server.
The database files will be created on the Virtual SQL Server per the database defaults of the SQL
Server. The Cisco TMS Tools application installed with Cisco TMS should be used to update SQL
connection settings post-install if required.
Maintenance
Users should regularly backup the SQL database. The interval between backups defines the
maximum time window over which data would be lost. Typical installations would perform full nightly
backups of the database. Please see Section
0 Backup and Recovery of the TMS database
of this
document for additional details on how to perform backups and restores of the Cisco TMS database.
Upgrading Cisco TMS
This installation model requires no additional steps or procedures to follow when performing upgrades
or patches.
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
Time to restore service.
For SQL Server, recovery is dependent on SQL Server configuration, normally on the order of
seconds to minutes. For the Cisco TMS Server, it is dependent on time to repair the server or
replace with another server on the same IP address and DNS hostname and perform a recovery.
Estimate a few hours to a day.
Administrative Capabilities Required.
Low for Cisco TMS Server portion, very high for SQL Cluster.
Cost.
High if the SQL Cluster does not already exist