Id reboot the whole cluster, then let it sit for about 6 hours. Then try again. Sometimes it takes quite awhile for replication to get settled. If not, reload the subscriber from scratch and start over. Takes only 2 hours at most. (then replication)
The problem sub had been on the cluster for two weeks with a bad replication status. The tac engineer tried multiple commands with no joy.
I then removed the sub and reinstalled. Still the same problem.
I believe that it was a bug in 6.1.3a adding a new sub to the cluster but the workaround did not work.
This rebuilt sub still had the issue so the tac engineer advised the clusterreset.
This is where I am at now.
I am thinking that maybe if I delete this problem sub from the publisher database and shut it down. Then rerun the clusterreset and see if I can get the cluster back to a status of 2 then perform a reboot.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...