Cisco Cisco E-Mail Manager Unity Integration Option Troubleshooting Guide

Troubleshooting Guide for Cisco Unified Contact Center Management Portal Release 8.0(1)

30 minutes (see Step 1, above) shut down the Data Import Server
service again. If there are still unfinished session directories, then
a double error has occurred in the platform. To correct this
problem, you must restore the database from backup before
proceeding with the import.

3. Assuming the services shut down correctly and there were no

unfinished session directories in the
TS_IMP_DIRECTORY_STATUS table, the next step is to
completely clear out the Replicated folder. This folder contains
imported information from the crashed server and cannot be
guaranteed. The data may also contain references to resources that
will never arrive as the SQL Server replication link is down.

4. Finally, set the import token to active and restart the Data Import

Server services. The process for restoring what was the active
importer is described in the next section.

Inactive Importer Server Crash

Another failure mode to consider is a server crash which is not the active
importer.

This scenario does not break import processing on the active importer.
Data continues to be imported on the active side, and session directories
accumulate in the ToReplicate folder. These session directories cannot be
replicated to the other side, as it is unavailable. They therefore quickly use
up available disk space.

The recommended approach is to re-configure Replication.xml on the
active importer and remove the crashed server. All entries in the
ToReplicate folder should then be deleted. This configuration change
stops the disk filling up on the active importer.