May 27, 2019 at 12:02 pm
Hello,
I have a question on sql always on on sqlserver 2012 EE.
I have created a 3 server environment, containing 1 DC and 2 SQL servers. Installed failover cluster on it. installed SQL2012 EE on both SQL nodes. configured an Availability Group (AG) and placed that in the cluster called sqlcluster with its corresponding ip.nr.
Now I have SQL1 as 192.168.56.181
SQL2 as 192.168.56.182
and sqlcluster as 192.168.56.185
Everything looks like it is working as expected. If I connect to 185 (SQLcluster) with sqlstudio, I am connected to the primary node.
If I reboot the primary node. the AG shifts to the other node. and my SQLcluster (185) is looking at the other node.
Now the issue.
When I stop sql server on the primary node. the AG shift to the other node, all fine, but the sqlcluster (185) still looks at the sqlserver which is down (only sql server services). If I start sql services on this node. I get access via the sqlcluster (185) but I am connected to the secondary node)
How can I make sure if the sqlcluster is also shifting to the correct node. I don't want to setup a services cluster failover, because then only one sqlserver is up, and basically no always on functionality is possible. or I need to manual start services on both nodes.
The only thing I need is to have the sqlcluster (185) looking at the correct (primary) server.
May 27, 2019 at 2:03 pm
What do you call "sqlcluster"?
Is it AG listener or anything else?
May 28, 2019 at 11:52 am
I think you pointed me in the correct direction. I did not had a listener.
Checking this now. if that brings the solution for my issue.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply