Cisco Cisco Unified Contact Center Enterprise 9.0(2) User Guide
Understanding the Historical Data Server
Historical data is stored in the ICM/IPCC Logger's central database and in the Historical Data
Server (HDS) on the Distributor Admin Workstation.
Server (HDS) on the Distributor Admin Workstation.
You must use the HDS if you want to use WebView for reporting. Using the Logger's central
database for reporting with WebView is not supported. The only exception to this is for the
System IPCC All-In-One deployments that are for lab use only.
database for reporting with WebView is not supported. The only exception to this is for the
System IPCC All-In-One deployments that are for lab use only.
Typically, you set up two Distributor Admin Workstations as HDS machines. The same
fault-tolerant strategy that applies to the real-time Distributor AW also applies to the HDS; that
is, when the primary HDS fails, the Client Admin Workstation automatically switch over to use
the backup HDS. In System IPCC deployments, the appropriate number of HDSs for your
configuration are installed automatically.
fault-tolerant strategy that applies to the real-time Distributor AW also applies to the HDS; that
is, when the primary HDS fails, the Client Admin Workstation automatically switch over to use
the backup HDS. In System IPCC deployments, the appropriate number of HDSs for your
configuration are installed automatically.
Relationship Between the Logger and Historical Data Server
Each Historical Data Server (HDS) is connected to a single Logger. The Logger's central database
replicates historical data to the HDS. The replication process may have a latency of about one
to five minutes because the Logger replicates data table-by-table on the HDS.
replicates historical data to the HDS. The replication process may have a latency of about one
to five minutes because the Logger replicates data table-by-table on the HDS.
You configure the number of days for which data is stored in the Logger central database and
the HDS. The Logger stores data for less time than the HDS. For example, you might store two
weeks of data on the Logger and a year of data on the HDS. You configure the amount of time
that data is stored on the Logger in relation to the schedule for HDS backups to ensure that you
do not lose data in the event that the HDS goes offline. When the HDS recovers after going
offline, it retrieves all of the data on the Logger for the interval for which data is missing from
the backup, and you manually restore the rest of the data from the last HDS backup. For example,
if the HDS backup has data up to the last two weeks, the HDS would replicate the last two weeks
of data from the Logger when recovering. The amount of data retained on the Logger cover, at
a minimum, the time period between HDS backups. For example, if the Logger stores data for
two weeks, then you need to back up at least every other week to ensure that you can recover
all historical data.
the HDS. The Logger stores data for less time than the HDS. For example, you might store two
weeks of data on the Logger and a year of data on the HDS. You configure the amount of time
that data is stored on the Logger in relation to the schedule for HDS backups to ensure that you
do not lose data in the event that the HDS goes offline. When the HDS recovers after going
offline, it retrieves all of the data on the Logger for the interval for which data is missing from
the backup, and you manually restore the rest of the data from the last HDS backup. For example,
if the HDS backup has data up to the last two weeks, the HDS would replicate the last two weeks
of data from the Logger when recovering. The amount of data retained on the Logger cover, at
a minimum, the time period between HDS backups. For example, if the Logger stores data for
two weeks, then you need to back up at least every other week to ensure that you can recover
all historical data.
Logger and Historical Data Server Failure and Recovery
If the Logger connected to the HDS goes offline, the HDS does not connect to a different Logger.
For example, if the HDS is connected to Logger B, it does not connect to Logger A if Logger
B fails. When Logger B comes back up, it recovers data from Logger A and begins to receive
current historical information. Once the Logger has recovered all of the data from Logger A, it
begins to replicate this data to the HDS. If reports are run from this HDS for recent intervals
while the Logger is offline, or while the Logger is in the process of recovering or replicating
data, you might not see data for those intervals in reports. This is temporary and you will see
the data once the replication process for the tables utilized by the reports is complete. If you are
using a fault-tolerant system with two HDS Distributor Admin Workstations, you can run reports
using the backup HDS while the primary HDS is not receiving data.
For example, if the HDS is connected to Logger B, it does not connect to Logger A if Logger
B fails. When Logger B comes back up, it recovers data from Logger A and begins to receive
current historical information. Once the Logger has recovered all of the data from Logger A, it
begins to replicate this data to the HDS. If reports are run from this HDS for recent intervals
while the Logger is offline, or while the Logger is in the process of recovering or replicating
data, you might not see data for those intervals in reports. This is temporary and you will see
the data once the replication process for the tables utilized by the reports is complete. If you are
using a fault-tolerant system with two HDS Distributor Admin Workstations, you can run reports
using the backup HDS while the primary HDS is not receiving data.
Reporting Guide for Cisco IPCC Enterprise & Hosted Editions 7.2(1)
38
Chapter 2: - Understanding Cisco IPCC Reporting Architecture
Understanding the Historical Data Server