Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers
m (1 revision)
Latest revision as of 18:59, 21 April 2011
Configuration and Recording meta data is not synchronized between Primary and Secondary Servers
|Problem Summary||When the secondary server joins the primary server in the same cluster, there may be a small time window during which the configuration and recording data written to the primary server is not replicated to the secondary server. This time window typically happens during the secondary server installation and configuration.|
|Possible Cause||This happens when secondary server joins the cluster. At that time, the secondary server takes a data snapshot from the primary server and then sets up data replication. There is a small window between the two steps, during which time the data written to the primary server is not copied to secondary server and the data becomes out-of-sync between the two servers.|
Run the following CLI command on secondary server after all services are activated, to sync up meta data with primary server:
That command will launch Informix data repair jobs. Run the following CLI command on secondary server to monitor the status of the jobs:
When all status is "C" (completed), jobs have completed successfully and meta data is in sync between the two nodes.
Please refer to Installation and Administration Guide for Cisco Media Capture Platform, Chapter 8, for more information on CLI commands.
|Release||Release 8.5(1) and 8.5(2).|
|Associated CDETS #||CSCtj33729|