User Guide

Reporting Implications of Data Loss and Component
Failover
The Cisco Unified ICM uses sophisticated techniques in gathering and storing data. Due to the
complexity of the system, the amount of data being gathered, the diversity of devices and
peripherals, and the complex processes involved, it is possible that WebView historical reports
might present inconsistent data.
Although these reporting inconsistencies are confusing, most can be traced to temporary effects
caused by time lags between the processes involved and nature of the data itself.
This chapter identifies and explains common conditions that lead to temporary and permanent
inconsistencies in historical data. It discusses the potential effect of system failover on data that
appears in WebView reports and offers guidance on how to guard against data loss.
This chapter contains the following topics:
•
Data Flow from Logger to Historical Data Server, page 143
•
Preventing Data Loss from Logger and HDS Failure, page 145
•
Data Loss from PIM Failure, page 148
•
Other Possible Points of Failover, page 148
Data Flow from Logger to Historical Data Server
Assuming a full-duplex, fault tolerant implementation, data is sent from Router A to Logger A
and from Router B to Logger B.
The Logger Central Database forwards (replicates) historical data to corresponding historical
tables on the Historical Database Server in summary half-hour intervals. These data populate
the historical half-hour and daily reports.
Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)
143
Chapter 10