Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Release Note
2-30
Cisco Unified Contact Center Express Solution Reference Network Design
Chapter 2 Cisco Unified Contact Center Express Solution Architecture for Cisco Unified Communications Manager
Cisco Unified CCX Fault Tolerance
MAC address from the Cisco Unified CM. Either of the two monitoring servers could be used for this
purpose. If one Monitoring component fails, recording still works, as long as the other server running
the Monitoring component is still available in the Cisco Unified CCX cluster.
purpose. If one Monitoring component fails, recording still works, as long as the other server running
the Monitoring component is still available in the Cisco Unified CCX cluster.
Cold Standby Support
Cisco Unified CCX high availability requires that the Cisco Unified CCX Engine and Database
components and the CTI Managers with which the Cisco Unified CCX servers communicate be located
in the same campus LAN and that the maximum round-trip delay between these servers be less than 2 ms.
components and the CTI Managers with which the Cisco Unified CCX servers communicate be located
in the same campus LAN and that the maximum round-trip delay between these servers be less than 2 ms.
For disaster recovery deployments where the backup Cisco Unified CCX servers need to be in a different
geographic location, Cisco Unified CCX high availability is therefore not supported. However, for this
requirement, it is possible to deploy identically configured cold standby servers in the disaster recovery
site. The cold standby servers and the corresponding primary servers should have the same IP addresses.
These cold standby servers at the second site should be shut down while the primary servers are in
service at the first site. If a disaster occurs and the primary site is down, the cold standby servers are
turned on, restored, and become the active servers.
geographic location, Cisco Unified CCX high availability is therefore not supported. However, for this
requirement, it is possible to deploy identically configured cold standby servers in the disaster recovery
site. The cold standby servers and the corresponding primary servers should have the same IP addresses.
These cold standby servers at the second site should be shut down while the primary servers are in
service at the first site. If a disaster occurs and the primary site is down, the cold standby servers are
turned on, restored, and become the active servers.
The cold standby servers can be restored using one of the following tools:
•
Backup and Restore tool
•
Ghost or similar imaging tool
For example, in the two-server high
availability deployment model, two cold standby servers can be added on the disaster recovery site.
When deploying cold standby, the following rules apply:
•
Use the Backup and Restore tool to backup the primary servers and restore the cold standby server.
For information about this tool, refer the Cisco Unified CCX Administration Guide
For information about this tool, refer the Cisco Unified CCX Administration Guide
OR
Use Ghost or similar imaging tool to take periodic snapshots of the primary servers and restore the
cold standby servers from those snapshot images. The snapshot images should be uploaded to a
central location accessible from both sites.
cold standby servers from those snapshot images. The snapshot images should be uploaded to a
central location accessible from both sites.
•
The deployment in the disaster recovery site must be identical to the deployment in the primary site
(same number of servers, same server type).
(same number of servers, same server type).
•
The cold standby servers should be shut down if the primary servers are running, and vice versa.
•
If the Backup and Restore tool is used to restore the cold standby servers, do not perform the Unified
CM Telephony Synchronization at the end of the restore process. If Cisco Unified CM Publisher is
down or inaccessible, the synchronization will fail because it needs access to the publisher to
perform write operation to Cisco Unified CM database.
CM Telephony Synchronization at the end of the restore process. If Cisco Unified CM Publisher is
down or inaccessible, the synchronization will fail because it needs access to the publisher to
perform write operation to Cisco Unified CM database.
•
The deployment at the disaster recovery site must follow the Cisco Unified CCX rules for design
that are described in
that are described in
For
example, when deploying with high availability at each site, the Cisco Unified CCX servers must
be located in the same Campus LAN and the round-trip delay between these servers should be less
than 2 ms.
be located in the same Campus LAN and the round-trip delay between these servers should be less
than 2 ms.
•
Once the image is restored, the Cisco Unified CCX servers at the disaster recovery site should have
the same IP addresses and hostnames as their corresponding servers at the primary site. However,
changing IP addresses on the Cisco Unified CCX servers is possible. In this case, follow the
procedure described in Cisco Unified CCX Administration Guide to change the IP addresses of the
Cisco Unified CCX servers. Also update every CAD and CSD desktop by running the postinstall.exe
program at C:\Program Files\Cisco\Desktop\bin on the desktop PC.
the same IP addresses and hostnames as their corresponding servers at the primary site. However,
changing IP addresses on the Cisco Unified CCX servers is possible. In this case, follow the
procedure described in Cisco Unified CCX Administration Guide to change the IP addresses of the
Cisco Unified CCX servers. Also update every CAD and CSD desktop by running the postinstall.exe
program at C:\Program Files\Cisco\Desktop\bin on the desktop PC.