Configuration: Configuration data is not synchronized between Primary and Secondary Servers

Revision as of 19:20, 24 November 2010 by Cchetty (Talk | contribs)

Configuration data is not synchronized between Primary and Secondary Servers

Problem Summary	When Secondary Server joins Primary Server in the same cluster, configuration data is not synchronized between the two servers after all services are activated on Secondary Node.
Error Message	None.
Possible Cause	This happens because, when Secondary Node joins the cluster, it takes a data snapshot from Primary Node, and then sets up data replication. There is a small window between the two steps, during which data will get out of sync between the two servers.
Recommended Action	Run the following CLI command on Secondary Node after all services are activated, to sync up config data with Primary Node: `run db_synchronization db_ora_config` That command will launch Informix data repair jobs. Run the following CLI command on Secondary Node to monitor the status of the jobs: `show db_synchronization status db_ora_config` When all status is "C" (completed), jobs have completed successfully and config data is in sync between the two nodes. See the Installation and Admin Guide for Cisco Media Capture Platform, Chapter 8, for more information on the CLIs.
Release	Release 8.5(1).
Associated CDETS #	CSCti87080

Rating: 0.0/5 (0 votes cast)