Dirsync is for the directory, not for CUCM DB.

use admin: utils dbreplication repair all to do so or do the following:

SUBSCRIBERS

admin: utils dbreplication stop

PUBLISHER

admin: utils dbreplication stop

PUBLISHER

admin: utils dbreplication reset all

HTH

javalenc

if this helps, please rate

Ok, sorry for the delay on this all. My goal here is if the Publisher dies (CUCM 6.1), then the Subscriber takes over without any issue. Well, when I took down the Publisher today (because I changed the default gateway on it), then the Subscriber didnt have the config I had initially put in for route patterns, etc. I had added two phones in on the Pub, but one wouldnt register because it was pointed to the Subscriber as the primary. To troubleshoot, I looked at the Subscriber to see why, and neither phone was there in the phones listing. The first one registered to the Publisher without issue. So, after the Publisher had rebooted and the gateway was correct, I had rebooted the Subscriber and then all was good. But, if the Publisher fails, I want the Sub to take over without issue, and not have to reboot it after the Publisher comes back up. Is there a way that this happens automatically?

CSCsk10706

CM 5.x and 6.x DB Interrupted duringReplicate setup needs to recover

HTH

javalenc

if this helps, please rate

All, I think I got this figured out. I put the sub as the first server, the pub second. I pull the network cable for the sub out, and phones register to pub. Put sub network cable back in and it re-registers to sub. I think this is how it should work. Thanks all.