Hi Team,
Thanks in Advance,
============================================
Let me first explain my environment
I've Region 1 which is my primary region and Region 2 which is my DR Region on Azure.
I've 2 SQL Servers in Region 1, with Basic Load balancer for Listener and configured in Sync Mode of Always ON AG.
I'm planning to create a Standard Load Balancer in DR Region for listener, and connecting the primary and secondary site using Global VNET Peering.
As the secondary region will only be used for DR, once my all/primary servers goes down in azure region then my DR region SQL Server will be reachable to the web app. we've parallel web app deployed in DR Region so that it can connect to the SQL Node in DR Region for DB.
============================================
I've few queries related to SQL Always ON AG on Azure VM between 2 Region.
As per the below article (Link 1), it is mentioned that we've to create VPN Gateway between the region for connecting the 2 VNET on Azure.
The limitation for not using the global vnet peering in sql always on AG in multi region deployment was that in global vnet peering resources in one region cannot connect to the Load balancer of the other region. (Mentioned in Link 2)
As the above limitation is removed if we use Standard Load balancer in DR Region (Link 3),I've 2 queries
Link 1 : https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-availability-group-dr
Link 2 : https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-peering-overview#requirements-and-constraints
Link 3 : https://azure.microsoft.com/en-in/updates/global-vnet-peering-now-supports-standard-load-balancer/
Query 1 :
If I use Global VNET PEERING to connect the region 1 and Region 2 with Basic Load Balancer on Both the ends for listener
Currently, resources/web apps in Region 1 will never connect to the DR SQL as we've web app/resources in Region 2 deployed which will connect to the SQL Node 3 in DR Region (When failover happens and my Primary Region is down). So does the limitation mentioned in the Link 2 applies in my scenario of DR?
In the above query 1, does SQL Node 1 or 2 in region 1 utilizes the listener IP/Load balancer on the DR Region for replication? or for any other reason? I believe Listener IP on LB is only used for the client connectivity.
I assume if i would have any web app from region 1 connecting to SQL Node 3 in DR region then the above limitation (Link 2)would have come into picture. But as we have web app in DR region deployed and will connect to the DR SQL Node at the time of failover/region down scenario then it would not make any impact and the limitation of global vnet peering does not applies to my scenario.
Query 2 :
If i create standard load balancer for listener in Region 2, and use Global VNET Peering to connect primary and DR VNET (Region 2). Does that help me in any ways? or overcome any blockers? and Will i be able to deploy SQL Always ON AG between 2 region/ multi region successfully?