Unified CVP lets
users turn the scheduling of data backups on or off, and to run backups on
demand. Backups are made to the reporting servers local file system. By
default, scheduled backups are turned off.
Unified CVP backup scheduling is an optional feature. Backup is the user's
responsibility. Data loss may occur if the backing up of files is not managed
properly by the user.
If Unified CVP
backup scheduling is turned on, the backup occurs once per day. Backups must be
scheduled to run no sooner than 30 minutes after the scheduled purge job.
Users can run a
backup on demand—as long as another backup, or a purge, is not already running.
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 are available
on the local machine. Retaining two backup files is critical. If the system
fails while writing a backup, and a restore is necessary, the older backup file
is required for restore.
It is a best
Keep a given
backup for at least two weeks.
integrity of the backup periodically.
Run a backup
before an upgrade.
Unified CVP uses
the Informix backup utility ontape (for both backup and restore).
When a new backup
launches—either scheduled, or on demand from the Operations Console—the new
file is named
cvp_backup_data.gz. The Unified CVP backup script
copies the previous
cvp_backup_data.gz backup file and renames it to
cvp_backup_data.old.gz. This always leaves two backup
files on the local system and makes it easy for Unified CVP administrators to
script copy jobs to move the files. The backup script ensures that two backups
cannot be launched at the same time.
Storing a backup on
the local machine does not protect against failure of that machine or loss of a
Important: You must manually or automatically create a job to copy the
cvp_backup_data.old.gz file to a separate machine,
preferably at a separate location. Again, the user is responsible for managing
script also ensures that a backup cannot be launched if a purge is underway,
and vice versa.
cvp_backup_data.old.gz file can be copied. The
cvp_backup_data.gz file cannot be copied. Attempting to
cvp_backup_data.gz file locks the file and prevent
another backup from running.
updates the log file when the backup finishes. If the database server goes down
during backup, the backup file gets corrupted.
To check if Informix
is up and running and to validate the backup, execute the
cvpverifybackup.bat file located at
While executing the
script, you are prompted with following message:
Please put in Phys Tape 1.
Type <return> or 0 to end:
Press 0 and press Enter
Based on the size
of the database, the prompt keeps changing as Tape 2, Tape 3 and so on.
execution takes a long time (based on the database size) to validate and the
results are displayed on the console.
In Cisco Unified
CVP, there is a supported script to perform a database restore.
Restoring a backup
image is required when older data on a backup image needs to be recovered. It
is also required when a machine is rebuilt after a hardware failure and you
need to recover data.
Although it is
possible to restore a backup image from one reporting server to another, such a
restoration is not supported with the CVP restore process.
The restore process
in Unified CVP is as follows:
CallServer process (Reporting Server).
Using a third-party backup utility to back up the Informix database is
ineffective and may be dangerous to the integrity of the reporting database.
The only effective way to perform a reporting database backup is with the
backup process provided by the OAMP interface.
For information on
configuring backups, see the
Administration Guide for
Cisco Unified Customer Voice Portal.