Cisco Redundancy Models for Cisco TMS
Cisco TMS redundancy configuration and overview
Page 26 of 32
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. After
the reboot, go into Services component of Computer Management, manually stop all services
whose name starts with Cisco TMS and the WWWPublishingService. The services may also be
configured for automatic startup. Right-click on each of these services and select Properties. On
the General tab of each of the services you stopped, set startup type to Manual.
If your deployment model has multiple servers, follow the steps for upgrading Cisco TMS per the
relevant section of this document.
Once the off-site location has been upgraded, log into the Windows console of the primary server
and restart all Cisco TMS services and WWWPublishingService service. Your upgrade is now
complete.
Model Summary
Immediate fail-over available.
Not for primary to secondary site, but possible to have automatic failover within a location.
Amount of data lost.
The intervals defined in your Log shipping configuration dictates out of date the secondary SQL server
is. Activity on the primary server since the last log shipment would be lost in a fail-over.
Time to restore service.
Variable on how long it would take to reconfigure devices and start-up the secondary server. Estimate
a half hour or more to activate the secondary site and update configurations to point to the new
secondary site.
Administrative Capabilities Required
High for configuring SQL Log Shipping and Managing cut-over to secondary site.
Cost.
High. Must implement multiple servers in multiple locations.
