Replication of the SQL database is a core function of Cisco CallManager
clusters. The server with the master copy of the database is called the
publisher, while the servers that replicate the database are called
subscribers.

In the event that your subscriber stops the replication of data from
the publisher, you need to rebuild the publisher/subscriber relationship(s). In
order to do this, go into the SQL Server database and manually rebuild the
subscription.

Symptoms

This is a list of possible symptoms if the subscriber stops replicating
from the publisher:

Changes that are made on the publisher are not reflected on phones
that are registered with the subscriber.

Outbound calls fail on phones registered with the subscriber. As soon
as you dial 9, you hear a re-order tone.

The information presented in this document was created from devices in
a specific lab environment. All of the devices used in this document started
with a cleared (default) configuration. If you work in a live network, ensure
that you understand the potential impact of any command before you use
it.

Complete these steps in order to reestablish the relationship between
the two systems. First, the subscription of the subscriber needs to be
recreated on the publisher. Then, the subscription needs to be deleted and
recreated on the subscriber system.

The subscription must be added back into the subscriber SQL server.
Select the SQL server name of the subscriber that you just deleted from the
publisher. In this configuration, the publisher is AVVID_LAB_PUB and the
subscriber is AVVID_LAB_SUB1. You have just deleted the AVVID_LAB_SUB1
subscription from the AVVID_LAB_PUB publication. In order to resubscribe to the
publication, choose the AVVID_LAB_SUB1 SQL server and select
the CCM0301 database. Right-click to get the menu. Then select
New > Pull Subscription from the menu.

Note: Always choose the latest version of the database, not the earlier
(CCM0301 in this example) version.

Click Next when the Pull Subscription Wizard
appears.

On the Choose Publication window, expand the publisher (which needs
to be listed) and select the CCM0301 database. Click
Next.

Select Using SQL Server Authentication of this
account on the Specify Synchronization Agent Login
window

. The login name is sa and the password is the same password as the
publishers 'sa' account.

Select Yes, make this an immediate-updating
subscription(s) on the Specify Immediate-Updating Subscription(s)
window. Then click Next.

Select Yes, initialize the schema and data at the
Subscriber on the Initialize Subscription window and click
Next.

Select Continuously on the Set Distribution Agent
Schedule window and click Next.

The next step verifies that both the SQL server agent and the
Microsoft DTC services run. Click Next.

Click Finish on the Completing the Pull
Subscription Wizard window.

The Wizard sets up the subscription and displays a success when
completed.

The Wizard sets up the subscription.

A display that indicates success appears when the process
completes.

Now that the subscription is created, the snapshot agent must be
run in order to get the data out to the subscriber for synchronization. Select
the publisher SQL server and navigate to Replication Monitor >
Publishers > Machine_name >CCM0301 subscription. Select the
Snapshot entry and choose Start. The snapshot
agent runs at this point. It takes about three to five minutes to complete the
task. Once the snapshot agent completes, the pull agent starts to apply the
snapshot to the subscriber. This takes another three to five minutes.

Once the pull subscription completes, on the publisher, select the
subscriber SQL server and open the pull subscriptions for the CCM0301 database.
The subscription needs to be in an active state and it needs to wait for
updates.

Note: If the last action still reads "Waiting for snapshot agent to
become available", press F5 in order to refresh the
screen.

At this time, the subscriber is now resynchronized with the
publisher and updates are recorded in the local subscriber SQL database.