Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Related Manuals for Cisco TMS SERVER REDUNDANCY - CONFIGURATION GUIDE 13.0
Summary of Contents for Cisco TMS SERVER REDUNDANCY - CONFIGURATION GUIDE 13.0
- Page 1 Cisco TMS Server Redundancy Configuration Guide D14570.02 December 2010...
-
Page 2: Table Of Contents
Cisco Revision Notes Contents Cisco TMS Server Architecture ....................... 6 Communication with Cisco TMS ......................6 Users Communicating with Cisco TMS .................... 6 Cisco TMS and Devices ........................6 IP Addresses vs. DNS hostnames ....................6 Cisco TMS and External Systems ....................7 Cisco TMS and Database ........................ - Page 3 Cisco Revision Notes Maintenance ........................... 25 Upgrading TMS ..........................25 Model Summary ..........................26 TMS Customer file synchronization ....................27 Backing up the database ........................29 Restoring the TMS Database ........................ 29 Event Execution ............................. 31 Conference Connection and Control ..................... 31 Figures Figure 1 Multiple Stand-by Server Illustration ..................
- Page 4 Cisco Revision Notes Revision Notes November 2010 Rebranded with Cisco Systems. September 2010 Applied Cisco template and Cisco product names Rev 2.1.1 Fixed Bookmarks in PDF Output. Rev 2.1 Added Validation Key requirements. Corrected viewstate comments. Added sticky connection recommendation for NLBs. Minor formatting changes.
- Page 5 Cisco Introduction Introduction The Cisco TelePresence Management Suite (Cisco TMS) supports installation into environments that can provide fail-over or redundancy for both the Cisco TMS server and Cisco TMS database. This document describes the requirements, configuration, and limitations when implementing Cisco TMS in a redundant or fail-over solution.
-
Page 6: Cisco Tms Server Architecture
Cisco Overview of Cisco TMS Structures and Communications Overview of Cisco TMS Structures and Communications Cisco TMS Server Architecture Cisco TMS functionality is achieved through the combination of several elements. Users only interact with Cisco TMS through the website, but the complete Cisco TMS product is actually constructed from three different logical components: Cisco TMS Web-Server: The web server used by Cisco TMS is Microsoft’s Internet Information Server (IIS). -
Page 7: Cisco Tms And External Systems
Cisco Overview of Cisco TMS Structures and Communications Cisco TMS and External Systems External systems such as Exchange Integration or IM integrations always communicate to Cisco TMS through the HTTP protocol. As such, the installation of these packages must always have the specific IP address or DNS hostname where Cisco TMS will be reachable. - Page 8 Cisco Redundancy Concepts for Cisco TMS Redundancy Concepts for Cisco TMS Redundancy for your Cisco TMS application can be achieved in several different ways depending on your requirements for availability. How long can you tolerate the application being unavailable? - Minutes? Hours? Days? Tolerance for data loss –...
- Page 9 Cisco Cisco TMS Architecture Requirements for Redundancy Cisco TMS Architecture Requirements for Redundancy Implementation of Cisco TMS in any redundant or fail-over model hinges on maintaining compatibility with several key concepts from Cisco TMS. The following hold true regardless of which redundancy model you choose to implement.
- Page 10 Cisco Cisco TMS Architecture Requirements for Redundancy validation key and method to ensure smooth transition if a user gets redirected between machines. Cisco TMS redundancy configuration and overview Page 10 of 32...
- Page 11 Cisco Changes from previous versions Changes from previous versions Cisco TMS version 11.0 and 11.5 included enhancements to Cisco TMS’s redundancy capabilities. For readers who were familiar with the previous Cisco TMS version 10.0 capabilities, the new improvements are outlined below. Snapshots now stored in database.
-
Page 12: Single Server, Single Database, Redundant Hardware
Cisco Redundancy Models for Cisco TMS Redundancy Models for Cisco TMS This section will outline each of the redundancy models covered in this document highlighting their concept, recovery models, advantages, disadvantages, installation, maintenance, and upgrade requirements. Single Server, Single Database, Redundant Hardware The first level of any redundant solution should consist of installing Cisco TMS onto a server-grade platform that includes: ECC Memory –... -
Page 13: Single Server, Separate Database
Cisco Redundancy Models for Cisco TMS Administrative capabilities required – Low, only requires basic skills and SQL backup/recovery procedures Cost – Low, cheapest alternative available Single Server, Separate Database The first level of any redundant solution should consist of installing Cisco TMS onto a server-grade platform that includes: ECC Memory –... -
Page 14: Maintenance
Cisco Redundancy Models for Cisco TMS 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. -
Page 15: Installation
Cisco Redundancy Models for Cisco TMS 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. -
Page 16: Multiple Servers, Manual Cutover
Cisco Redundancy Models for Cisco TMS 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. -
Page 17: Installation
Cisco Redundancy Models for Cisco TMS Installation Using multiple Cisco TMS Servers requires the use of a separate SQL server, either stand-alone or clustered. Stand-alone SQL Server The separate SQL Server should be installed and operational prior to installing Cisco TMS. You do not need to perform any special operations on the SQL server prior to Cisco TMS installation except ‘mixed mode authentication’... -
Page 18: Set Web Validation Key On Web Servers
IIS generate its own which is the default behavior. The machinekey behavior can be controlled using the web.config file used by the Cisco TMS web application. This file is located in the wwwCisco TMS directory (default c:\program files\tandberg\tms\wwwCisco TMS) The behavior of this element is described in the following Microsoft articles http://msdn2.microsoft.com/en-us/library/w8h3skw9(VS.71).aspx... -
Page 19: Upgrading Tms
Cisco Redundancy Models for Cisco TMS 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. -
Page 20: Multiple Tms Servers, Load Balancing, And Clustered Database
Cisco Redundancy Models for Cisco TMS Multiple TMS Servers, Load Balancing, and Clustered Database The highest availability configuration is one that will provide automatic fail-over for both the Cisco TMS Server and the SQL database. Automatic Fail-over for the SQL database is discussed in Section Single Server, Clustered Database. - Page 21 Cisco TMS web application. This file is located in the wwwCisco TMS directory (default c:\program files\tandberg\tms\wwwCisco TMS) The behavior of this element is described in the following Microsoft articles http://msdn2.microsoft.com/en-us/library/w8h3skw9(VS.71).aspx...
-
Page 22: Maintenance
Cisco Redundancy Models for Cisco TMS Create a machinekey element using Microsoft’s supplied methods or from the sample websites listed above. Open the web.config file under the wwwCisco TMS directory and insert the new machinekey element text under the existing <system.web> element in the document. You must update the web.config file on each of the Cisco TMS servers. -
Page 23: Model Summary
Cisco Redundancy Models for Cisco TMS installation completes and the server reboots if necessary. Repeat these steps one server at a time until all Cisco TMS servers have been upgraded Once all Cisco TMS servers have been upgraded, you may restart all Cisco TMS services and WWWPublishingService on all Cisco TMS servers. -
Page 24: Recovery Methods
Cisco Redundancy Models for Cisco TMS The secondary SQL server is not always a current version of the database, as updates are ‘batched’ job transferred to the secondary server. Shipping intervals are defined in the SQL Server The bandwidth and processing required to ship updates to the back-up server limits how frequently you can update the back-up server The secondary Cisco TMS server must be kept offline and disabled until the off-site is brought online to be the primary site. -
Page 25: Maintenance
Cisco Redundancy Models for Cisco TMS After the Cisco TMS installation completes, you will be prompted to reboot the server. Reboot the server. After the server restarts, you must make the Cisco TMS portion of the server inactive by stopping all the Cisco TMS and Web services and setting them to manual startup. Open the Services tool from Administrative Tools in the Windows smart menu, and stop all services whose name starts with Cisco TMS and the WWWPublishingService service. -
Page 26: Model Summary
Cisco Redundancy Models for Cisco TMS Log into the Windows console of the off-site Cisco TMS server and start the upgrade or patch installer the same as you did on the first Cisco TMS server. The installer will likely restart the Cisco TMS services and WWWPublishingService and may require a reboot of the server. -
Page 27: Tms Customer File Synchronization
Cisco TMS servers, these files must be synchronized between the different servers. These files are located in the following directories in a default installation: c:\program files\TANDBERG\TMS\wwwCisco TMS\Data\CiscoSettings c:\program files\TANDBERG\TMS\wwwCisco TMS\Data\CompanyLogo c:\program files\TANDBERG\TMS\wwwCisco TMS\Data\EmailTemplate c:\program files\TANDBERG\TMS\wwwCisco TMS\Data\image... - Page 28 Create a text file with the following lines, and save as c:\SyncCisco TMSData.bat . The variables Cisco TMS_DATA_ROOT_SOURCE and Cisco TMS_DATA_ROOT_DEST should be updated based on your Cisco TMS installation’s details SET TMS_DATA_ROOT_SOURCE=c:\program files\TANDBERG\TMS\wwwTMS\Data SET TMS_DATA_ROOT_DEST=\\TMSServer2\c$\program files\TANDBERG\TMS\wwwTMS\Data xcopy "%TMS_DATA_ROOT_SOURCE%\CiscoSettings\*"...
-
Page 29: Backing Up The Database
Cisco Backup and Recovery of the TMS database Backup and Recovery of the TMS database Cisco TMS utilizes a standard Microsoft SQL database and server, so any compatible SQL tools may be used to backup and recover the database. The database can be backed up at any time without interrupting Cisco TMS service, but the database can not be in use when performing a database restore. - Page 30 Cisco Backup and Recovery of the TMS database SQL server named ACME\WIDGETS from a backup file c:\tmsbackup.bak enter the following command in a command window on the database server osql –U sa –S ACME\WIDGETS –Q “restore database tmsng from disk = ‘c:\tmsbackup.bak’”...
-
Page 31: Event Execution
Cisco Cisco TMS Redundancy limitations and notes Cisco TMS Redundancy limitations and notes This section will outline functionalities that may be affected or operate differently when using Cisco TMS in a redundant fashion. Event Execution Events that have already begun to execute by a particular server will not be completed by another server if the executing server fails. - Page 32 Cisco Cisco TMS Redundancy limitations and notes THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.