Cisco Cisco MediaSense Release 8.5(1) Guía De Instalación

High Availability in Unified MCP Deployments

Some deployment scenarios require all available media to be recorded. The high availability

feature is imperative for 

 deployed in these scenarios. A 

 failure may end up with no recordings unless your deployment

supports high availability. If the Unified CM application is unable to contact one of the Unified

MCP servers, you must ensure that an alternate server is available for Unified CM to make the

required connection.

Considerations for Data Replication

Database high availability support in Unified MCP deployments is provided using Informix

Enterprise Replication (ER) for both the Meta database and Config database. While an Unified

MCP cluster can have up to three servers, data replication is only enabled between the primary

server and secondary server.

At installation time, if the server being installed is identified as a secondary server, then the

following considerations apply to this server:

•

This server will automatically apply the ontape backup from the primary server without any

constraints on the data size in the primary node.

•

Data replication is performed between the primary and secondary servers. So, data written

to the primary server is also replicated to the secondary server, and vice versa.

The replication behavior between the primary and secondary Unified MCP servers differs based

on the time of replication:

•

:During the service activation process, Informix ER automatically begins

replication between the primary and secondary servers. The differential data between both

servers are replicated from the primary server to the secondary server.

•

: During run time, data replication is bidirectional. For any reason, if the one of the

Unified MCP servers is shutdown or in a failed state, data continues to be written to the

surviving server. When the shutdown/failed server is revived, Informix ER automatically

restarts between the two servers and synchronizes the data. Depending on the data size, this

synchronizing time may vary. Retention period refers to the numbers of days for which data

can be stored on the surviving server, without breaking the replication. See the Unified MCP
Solution Reference Network Design

 guide for details on the database retention period

recommendations.

Considerations for Unified MCP High Availability Deployments

Follow these guidelines to ensure highly-available deployment and to provide data replication:

Installation and Administration Guide for Cisco MediaSense 8.5(1)