September 21, 2017 at 11:09 am
Hello all!
We recently had an issue with AD / DNS / Domain Controllers, and now there is a weird mismatch.
WSFC Current Host Server is listed as :SERVERNAME2 , which is the Read_Only Secondary.
AlwaysOn High Availability Group primary is listed as: SERVERNAME1, which is the Read/Write primary.
Connecting VIA the listener (with read_only intent) connects to SERNAME2
Connecting VIA cluster name connects to SERVERNAME2
I could use a little insight on what potential issues this is causing, the host server being mismatched, and if I change it back to the original (through the Failover Cluster Manager) will this cause downtime? None of the applications or users connect VIA cluster name, we use the listener.
Any insight would be welcome!
Thank you.
January 12, 2018 at 12:36 pm
Have not gotten a direct answer to this yet, but it did not seem to cause any issues.
Since we do not have a SQL Cluster, and are just using the windows cluster for the Always On Availability group, it seems like we are fine.
If a forum admin sees this, please let me know if I should leave this as open or just close it.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply