Manual

Unied CVP uses the Informix backup utility ontape (for both backup and restore).
Unied CVP names backup les as follows. When a new backup launcheseither scheduled,
or on demand from the Operations Consolethe new le is named cvp_backup_data. The
Unied CVP backup script has been written to rst copy the last backup le cvp_backup_data
to cvp_backup_data.old. This always leaves two backup les on the local system and makes it
easy for Unied CVP administrators to script copy jobs to move the les. The backup script
ensures that two backups cannot be launched at the same time.
Note: The backup script also ensures that a backup cannot be launched if a purge is underway,
and vice versa.
Storing a backup on the local machine does not protect against failure of that machine or loss
of a site. Cisco strongly recommends that customers manually or automatically create a job to
copy the cvp_backup_data.old le to a separate machine, preferably at a separate location.
Again, the user is responsible for managing backup data.
Note: Only the cvp_backup_data.old le can be copied. The cvp_backup_data le can not
be copied. Attempting to copy the cvp_backup_data le will lock the le and prevent another
backup from running.
For information on conguring backups, see Chapter 3, "Conguring the Reporting Server"
(page 17).
Retries: Backup and Purge
Occasionally, a backup or purge cannot run when scheduled. For example, if an on-demand
backup is running when a purge is scheduled to run, the purge will be prevented from running.
Retries of scheduled backups or purges are performed according to the following rules.
Note: There are no retries for an on-demand backup.
A scheduled backup retries every 10 minutes, for up to 4 hours.
A purge retries every 10 minutes, for up to 6 hours.
At the end of 4 hours (for a backup) or 6 hours (for a purge), if the operation has not succeeded,
retries stop and an SNMP alert is sent.
If both a backup and a purge are retrying simultaneously, there is no guarantee as to which
operation will run rst.
If a lock (the mechanism preventing a backup or purge from running) is over 12 hours old,
the system clears it.
Reporting Guide for Cisco Unified Customer Voice Portal Release 4.1(1)
13
Chapter 2: Managing the Database
Retries: Backup and Purge