Table of Contents
Advertisement
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 – How much data can you lose without causing a significant impact? How
much data can you afford to lose in a recovery or fail-over? None? A few minutes? A few hours?
A day?
Administrative capabilities – What resources and skill sets does your organization have internally
to administer and configure network and server systems
Budget/Cost – How much is the organization willing to invest to in networking and server
resources to achieve higher availability or fault tolerance for the Cisco TMS application
In general, the higher your demands for accessibility and fault tolerance, the higher the cost and
complexity of the redundancy solution. Each solution has pros and cons and administrators must
choose which model best suits their business needs.
The redundancy models that can be used with Cisco TMS are:
Single Server, Single Database, Redundant Hardware
Single Server, Separate Database
Single Server, Clustered Database
Multiple Servers, Manual Cutover
Multiple Cisco TMS Servers, Load Balancing, and Clustered Database
Manual Off-Site Fail-over
This document will explain the details of each of these scenarios and in addition outline the
requirements of Cisco TMS for any redundancy solution.
Cisco TMS redundancy configuration and overview
Cisco Redundancy Concepts for Cisco TMS
Page 8 of 32
Advertisement
Table of Contents
