03-18-2008 03:00 PM - last edited on 03-25-2019 07:40 PM by ciscomoderator
Hi all.
I have a question about CallManager and SQL clustering.
Two server in a CallManager cluster, one Pub and one Sub.
The Pub need to be shut down. After Pub goes already up and running, Sub report "pull subscrption failed from Pub" in SQL enterprise manager.
The only way to reestablish subscrption is via Sub sever restart.
It should not be an automatic action?
The subscription should not restart automatically after a given amount of time?
Thanks
Solved! Go to Solution.
03-19-2008 05:49 PM
no, the replication can break and it's not reestablished automatically. that's why we provide the DBLHelper so you don't have to go thru all the process of recreating the publication and subscriptions directly in SQL which can be a painful process if you don't know the drill
The Republish button deletes the current subscription and recreates it. The Reinitialize button reinitializes all subscriptions and starts the snapshot agent. It also attempts to rebuild the subscription with the current database.
javalenc
03-18-2008 04:02 PM
It will try for a while but once it times out, it will give up. You can also go in SQL and manually restart replication.
Or do a query on the Cisco site for a utility called DBLHelper and that is the Cisco TAC approved way to do it.
03-19-2008 01:26 AM
Hi.
I know how to reestablish subscrition and replication (manually and using DBLHelper) but Cisco documentation tells that:
"The publisher replicates a read-only copy of the master database to all other servers in the cluster. If changes are made in the publisher's master database during a period when another server in the cluster
is unreachable, the publisher will replicate the updated database when communications are
re-established."
I suppose that when communications are
re-established replication is re-created automatically.
03-19-2008 05:49 PM
no, the replication can break and it's not reestablished automatically. that's why we provide the DBLHelper so you don't have to go thru all the process of recreating the publication and subscriptions directly in SQL which can be a painful process if you don't know the drill
The Republish button deletes the current subscription and recreates it. The Reinitialize button reinitializes all subscriptions and starts the snapshot agent. It also attempts to rebuild the subscription with the current database.
javalenc
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide