Cisco Redundancy Models for Cisco TMS
Cisco TMS redundancy configuration and overview
Page 12 of 32
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 – To protect against memory failure.
RAID Disks – To protect against hard drive failure.
Redundant Power Supplies – To protect against power supply failure.
These steps provide the first line of defense against an equipment failure and should be part of any
high availability Cisco TMS installation. In this scenario, the Cisco TMS server and SQL server are
installed on the same server, so if this server were to be taken offline due to network or equipment
failure, Cisco TMS would be unavailable. There is no direct fail-over available, but service can be
restored quickly by getting the server back online, or replacing the server with another using the same
IP and configuration.
Recovery Methods:
Repair the existing server and bring it back online
or
Replace failed server with new server using same IP address as original Cisco TMS. Install a new
copy of Cisco TMS. Restore customer specific Cisco TMS data files (See Section
0 Customer
specific TMS Files
) and restore the SQL database from backup (See Section
0 Backup and
Recovery of the TMS database
).
Installation
The Cisco TMS installation program allows selecting where to install the Cisco TMS software on the
local disks as part of the custom installation. Cisco TMS should be installed onto the RAID portion of
the hard disks. Setup and Maintenance of the redundant features of the server platform are provided
by the server vendor.
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
Backup and Recovery of the TMS database
section 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 the normal upgrade process for
Cisco TMS.
Model Summary
Immediate fail-over available – No
Amount of data lost – Call data during outage can be lost for some system types. No system or
configuration data lost if restored from database backup. Call and Scheduling information created
since last backup will be lost if the database is restored from a backup
Time to restore service – Dependant on time to repair the server or replace with an another server
and restore backups (estimate from a few hours to a day)
