The
Replication Servers menu option in
Datastore
Control Center allows you to view replication status and reset the
replication between two nodes for the data stores across all servers in the
cluster. This menu will be available only in a High Availability deployment.
By
default, replication between two nodes is removed if they are not able to
synchronize with each other due to network outage for a substantial period of
time. This time depends on the amount of requests sent from one node to the
other and the load on servers. If the replication stops due to network outage,
an alert is sent to the administrator so that the administrator can take
corrective action.
If the
replication is removed, the administrator can go to
submenu from the
Cisco
Unified CCX
Serviceability menu and click Reset Replication. This ensures that the
replication is established between the nodes and the data synchronization
(repair) process is initiated. Click
Check
Details icon to monitor status of the repair.
If the
network outage did not result in the replication setup being removed, after the
network is functional, the synchronization of data between the databases will
be automatic. For outages that last a few seconds, typically the administrator
need not take any action, and the system will be able to synchronize
automatically.
Note |
Even though the
replication between the nodes is removed, data can still be written to the
database, which is accessible to the
Unified CCX
engine.
|
When the
subscriber node is not functional and it is required to make configuration
updates from the publisher, you can disable Config Data store (CDS) and
Historical Data store (HDS) on the subscriber using
Disable
CDS and HDS icon or button. After the subscriber node is
functional, you can enable CDS and HDS on the subscriber using the same toggle
button.
Caution |
Any
configuration in Application Administration and Historical data on the
Subscriber node will be overwritten, when CDS is enabled again.
|