Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) 管理员指南
12-3
Cisco Unified CCX Administration Guide, Release 7.0(1)
Chapter 12 Managing Unified CCX Datastores
About Unified CCX Datastore
Internally, Unified CCX datastores use the Microsoft SQL Server merge
replication model. This means that a publisher is associated with a snapshot agent
and a subscriber is associated with a subscription agent.
replication model. This means that a publisher is associated with a snapshot agent
and a subscriber is associated with a subscription agent.
•
Snapshot agent. Generates a snapshot or image of the current database data.
For the Unified CCX datastores, usually a new snapshot is generated only
when the publisher is created or a subscriber is added. However, the Unified
CCX administrator has the option of manually triggering a snapshot.
For the Unified CCX datastores, usually a new snapshot is generated only
when the publisher is created or a subscriber is added. However, the Unified
CCX administrator has the option of manually triggering a snapshot.
•
Subscription agent. Actively replicates data between the publisher and
subscriber. Since Unified CCX uses bidirectional replication, the
subscription agent will replicate data from publisher to subscriber as well as
from the subscriber to the publisher.
subscriber. Since Unified CCX uses bidirectional replication, the
subscription agent will replicate data from publisher to subscriber as well as
from the subscriber to the publisher.
New nodes added to the cluster having datastores will not have any replication
role or type. In a multiple node cluster, the first node becomes the publisher only
when the second node is activated, and the second node becomes the subscriber.
role or type. In a multiple node cluster, the first node becomes the publisher only
when the second node is activated, and the second node becomes the subscriber.
A datastore with replication can play the following roles:
1.
Unknown/Deactivated
2.
Subscriber
3.
Publisher
A datastore can only move up or down the line of roles one step at a time. For
example, a publisher cannot be deactivated, so you first need to change the
publisher to a subscriber and then deactivate the subscriber.
example, a publisher cannot be deactivated, so you first need to change the
publisher to a subscriber and then deactivate the subscriber.
Also note that, while Unified CCX administrators can configure a publisher, they
cannot configure a subscriber. Subscribers are managed automatically by Unified
CCX; the event that triggers a datastore to play the role of a subscriber is the
datastore component activation.
cannot configure a subscriber. Subscribers are managed automatically by Unified
CCX; the event that triggers a datastore to play the role of a subscriber is the
datastore component activation.
You use the Unified CCX Datastore Control Center to manage and monitor these
agents.
agents.
Inactive Retention Period
By default, a subscriber is dropped from the publisher during a merge replication
if the subscriber did not synchronize with the publisher within the retention period
of two or four days. If a subscriber is dropped under these circumstances, use the
Unified CCX Datastore Control Center to prevent data loss.
if the subscriber did not synchronize with the publisher within the retention period
of two or four days. If a subscriber is dropped under these circumstances, use the
Unified CCX Datastore Control Center to prevent data loss.