Hello! This might not be the best place to post this since my issue also involves some infrastructure and Azure, but alas, this is a starting point.
I'm trying to set up in Azure a SQL AO HA cluster as IaaS on 2 SQL server 2017 machines, and it seems to be configured and working mostly.
SQL Server 2017 has a single listener, which is on its own "virtual" IP that is ping-able only on the primary SQL server (not sure if this is standard and desired behavior).
Replication works between both servers properly, as do switching in the Failover cluster and SQL AO HA between primary and secondary.
The Windows Cluster has its own "virtual" IP that is different from the VMs and from the Listener.
Now, the problem is that while this is all and good, the cluster used to be able to communicate as one computer via the DNS SQL-01 which has the same address as the Cluster's Virtual IP. This no longer is the case, and I even opened up ports 1433 and 5022 on both machine's Windows Firewalls firewalls.
To get around this and my applications, some of which are legacy and can't check for the listener port and the two IPs for the SQL servers, I decided to go ahead and use an Azure Load Balancer (Layer 4), and configuring port 1433 on its rules (that's the only one configured) together with floating IPs (which is recommended for this specific use case).
I still have not gotten the front-end IP to talk talk to my applications, and the back end is both of my SQL servers on port 1433.
Any suggestions would be greatly appreciated.
I'm trying to set up in Azure a SQL AO HA cluster as IaaS on 2 SQL server 2017 machines, and it seems to be configured and working mostly.
SQL Server 2017 has a single listener, which is on its own "virtual" IP that is ping-able only on the primary SQL server (not sure if this is standard and desired behavior).
Replication works between both servers properly, as do switching in the Failover cluster and SQL AO HA between primary and secondary.
The Windows Cluster has its own "virtual" IP that is different from the VMs and from the Listener.
Now, the problem is that while this is all and good, the cluster used to be able to communicate as one computer via the DNS SQL-01 which has the same address as the Cluster's Virtual IP. This no longer is the case, and I even opened up ports 1433 and 5022 on both machine's Windows Firewalls firewalls.
To get around this and my applications, some of which are legacy and can't check for the listener port and the two IPs for the SQL servers, I decided to go ahead and use an Azure Load Balancer (Layer 4), and configuring port 1433 on its rules (that's the only one configured) together with floating IPs (which is recommended for this specific use case).
I still have not gotten the front-end IP to talk talk to my applications, and the back end is both of my SQL servers on port 1433.
Any suggestions would be greatly appreciated.