If both the primary and secondary server are online but the secondary server is the "active" server. Are the changes that are made while the secondary server is active, immediately replicated back to the primary?
While in this scenario what should things look like under the replication monitor on the primary server DB while the secondary server is active.
Did you ever figure this out? We are running into the same thing. Changes made on the active server (in this case the secondary server) are not being replicated to the inactive server (primary server).
I am sure that failoverconfig.exe needs to be run again on both the primary first and then the seconday. Read this doc. Even though you are not changing IPs the doc goes through testing replication both ways.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.