01-07-2014 05:20 AM - edited 03-19-2019 07:42 AM
Hello.
We have a production environment with one publisher and two subscriber, all of these running 6.1.5 release.
All was ok until last friday, when we have tried to ugrade publisher to release 9.1.2 and it has failed.
So, we have performed a reinstallation of release 6.1.5 on publisher hw (an msc machine), and then we have performed a restore from last good backup.
After this restore, all it seems to work well, but phones registered to subscribers don't accept configuration changes.
If we made a change to a phone configuration, I can see change succesfully replicated to subscribers, but not to the phones.
If we try to reset phones that are registered to the publisher, it works.
If we try to reset phones that are registered to the subscriber, it DOESN'T works.
If we manually reset phones that are registered to the subscriber, it DOESN'T works (phones restart with old configuration).
I don't know where is the problem, any suggestion will be greatly appreciated...
Daniele
Solved! Go to Solution.
01-08-2014 01:48 AM
Hi Daniele,
A simple cluster reboot should be good enough in this scenario as the symptoms clearly point to database replication related issue here.
Manish
01-07-2014 08:53 AM
Did you perform a cluster reboot after the restore, it is mandatory. If the cluster reboot has already been done, please check the database replication using RTMT and see if the subscribers have any value other than 2.
HTH
Manish
01-08-2014 12:47 AM
Thanks Manish.
I've rebooted only publisher (because I've restored only that machine).
Do I need to reboot also all subscribers?
Do I need to restore also them?
Thanks.
Daniele
01-08-2014 01:48 AM
Hi Daniele,
A simple cluster reboot should be good enough in this scenario as the symptoms clearly point to database replication related issue here.
Manish
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