Cisco Cisco IPCC Web Option Guía Del Usuario

configuration, the bigger the HDS must be to store data. For example, the historical Call
Type database tables store data for each call type for each five minute and half hour interval.

The amount of time that you want to retain data on the HDS also affects database size. Decide
how long you want to retain reporting data before it is purged automatically from the databases.
Data beyond the configured retention time is purged automatically each day at 12:30.

You can use the ICM/IPCC Database Administration (ICMDBA) tool to estimate the sizes
of your databases. The tool prompts you for your configuration information and the amount
of time that data is retained in the databases.

•

In System IPCC deployments, the HDS size is configured automatically during installation.
During configuration, you determine how long you want to retain reporting data before it is
purged automatically from the databases. Data beyond the configured retention time is purged
automatically each day at 12:30.

•

Determine how you want to back up the HDS.

You can back up the HDS either while the HDS is running or while it is offline (generally
when the contact center is closed or during a time with low call volume).

Generally, performing a backup during peak hours while running is not recommended.
Backing up while the HDS is running might impact performance, especially if you are backing
up a large amount of data. While the HDS database is being backed up, new data from the
Logger is stored in the transaction log. If the transaction log reaches it maximum capacity
before the HDS has completed the backup, updates to the database stop until an administrator
manually empties the log.

Instead, back up at a regularly scheduled time when the contact center is not busy. You can
also take the HDS offline and perform a backup. However, the HDS is not available for
reporting when offline. If you plan to back up the HDS database while offline, you might
want to configure a secondary HDS to use for reporting during the backup interval.

•

Determine the HDS backup schedule and the number of days for which data is retained on
the Logger.

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 data from the Logger for the interval for which
data is missing from the 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 from a failure. 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 after a HDS failure.

•

Decide how many Historical Data Servers you require. For System IPCC deployments, the
required number of HDSs are installed automatically for your selected deployment.

Reporting Guide for Cisco IPCC Enterprise & Hosted Editions 7.0(0)