Cisco Cisco IPCC Web Option Maintenance Manual

For more information, refer to the link: 

.

Backup and Restore

A database can be lost or corrupted for several reasons, such as:

•

Disk drive failure

•

Bad media

•

Software error (in the Database Manager or elsewhere in the system)

Because you cannot protect against all these conditions, you must have a backup strategy in
place. This is especially important if you have a simplexed central database configuration.
However, even for a duplexed system, you still need to perform backups to protect against
software problems that corrupt both sides of the system.

Database

The following database backup strategies are commonly used:

•

Regularly scheduled database backups

•

Mirrored disk configurations

•

Redundant Array of Inexpensive Disks (RAID) configurations

Although the last two strategies might decrease system performance, they have the advantage
of not requiring manual intervention. However, while these configurations protect against disk
drive failure and bad media, they might not protect against some software errors.

In a simplexed database configuration, you need to ensure protection against all types of errors.
To protect your data, regularly back up the central database.

To perform a database backup, use the SQL Administrator tool provided with SQL Server.

Note: The SQL Monitor service must be running during a backup. If SQL Server is not
configured to start SQL Monitor automatically, you must start the service manually before
beginning the backup.

When you restore a database, you can only restore up to the last backup. Any transactions after
that backup are lost. Therefore daily backups are recommended for simplexed systems.

Note: You must backup the entire database at each backup interval. The system software does
not support the use of transaction log dumps as incremental backups.

Administration Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 8.x