Cisco Cisco Unified Customer Voice Portal 11.0(1)
Data Categories
The following data categories exist for Unified CVP. Note that a high level category, such as
Call, cannot have a lower retention time than a dependent category, such as CallEvent. For each
category, the default data retention times, in days, is given within parentheses.
Call, cannot have a lower retention time than a dependent category, such as CallEvent. For each
category, the default data retention times, in days, is given within parentheses.
level 1:
Call
(30)
level 2:
-Call Event
(30)
level 2:
-VoiceXML Session
(30)
level 3:
--VoiceXML Element
(15)
level 4:
---VoiceXML ECC Variable
(15)
level 4:
---VoiceXML Interact Detail
(15)
level 4:
---VoiceXML Session Variable
(15)
level 4:
---VoiceXML Element Detail
(15)
Database Backup
Unified CVP allows users to turn the scheduling of data backups on or off, as well as to run
backups on-demand. Backups are made to the Reporting Servers' local file system. By default,
scheduled backups are turned off.
backups on-demand. Backups are made to the Reporting Servers' local file system. By default,
scheduled backups are turned off.
Caution: Unified CVP backup scheduling is an optional feature. Backup is the responsibility
of the user. Data loss may occur if the backing up of files is not managed appropriately
by the user.
of the user. Data loss may occur if the backing up of files is not managed appropriately
by the user.
If Unified CVP backup scheduling is turned on, the backup frequency is once per day. Backups
should be scheduled to run no sooner than 3 hours after the scheduled purge job.
should be scheduled to run no sooner than 3 hours after the scheduled purge job.
Additionally, users can run a backup on demand—as long as another backup, or a purge, is not
already running. All database backups are performed and stored on the local machine. Due to
space limitations, a maximum of two backups and a minimum of one backup will be available
at any time on the local machine. Having two files is critical. If the system was to fail while
writing a backup, and the failure was such that a restore is necessary, the older backup file would
be required for restore.
already running. All database backups are performed and stored on the local machine. Due to
space limitations, a maximum of two backups and a minimum of one backup will be available
at any time on the local machine. Having two files is critical. If the system was to fail while
writing a backup, and the failure was such that a restore is necessary, the older backup file would
be required for restore.
It is a best practice to:
• Keep a given backup for at least two weeks
• Check the integrity of the backup periodically
Reporting Guide for Cisco Unified Customer Voice Portal Release 7.0(2)
14
Chapter 3: Managing the Database
Data Categories