Cisco Cisco Customer Voice Portal 8.0(1)

Pagina di 132
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.
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.
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 were 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.
Run a backup before an upgrade.
Unified CVP uses the Informix backup utility ontape (for both backup and restore).
Unified CVP names backup files as follows. 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.
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 Systems strongly recommends that customers 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 backup data.
Note: 
Only the 
cvp_backup_data.old.gz
 file can be copied. The 
cvp_backup_data.
gz
fi
le cannot be copied. Attempting to copy the 
cvp_backup_data.gz
 file will lock the file
and prevent another backup from running.
In Cisco Unified CVP, there is a supported script to perform a database restore.
There are two reasons why you would want to restore a backup image. The first would be in
the event that older data on a backup image needs to be recovered. The second reason would
be the case of a machine that has been rebuilt after a hardware failure, where you would want
to recover as much data as possible.
Reporting Guide for Cisco Unified Customer Voice Portal Release 8.0(1)
103
Chapter 5: Managing the Database
Database Backup