How to check if global virtual network peering is supported on the virtual cluster for SQL MI
Published Sep 23 2022 10:31 AM 1,412 Views
Microsoft

In this blog post we are going to describe how to check if global virtual network peering is supported on the virtual cluster hosting this instance.

 

If you are interested in other posts on how-to discover different aspects of SQL MI - please visit the http://aka.ms/sqlmi-howto, which serves as a placeholder for the series.

 

The auto-failover groups feature allows you to manage the replication and failover of all user databases in a managed instance to another Azure region.

One of the most important requirements is that the connectivity between the virtual network subnets hosting the primary and secondary instance must be established and maintained for uninterrupted geo-replication traffic flow.

While there are multiple ways to provide connectivity between the instances, global virtual network peering is the recommended way for establishing connectivity between two instances in a failover group. It provides a low-latency, high-bandwidth private connection between the peered virtual networks using the Microsoft backbone infrastructure. No public Internet, gateways, or additional encryption is required in the communication between the peered virtual networks.

 

Global virtual network peering is supported for instances hosted in subnets created since 9/22/2020.

 

How to check if global virtual network peering is supported on the virtual cluster hosting this instance?

 

1. Navigate to the managed instance in Azure Portal and select ‘Diagnose and solve problems’ option in the left menu:

NikoNeugebauer_0-1663952431858.png



2. Pick the ‘Failover Groups’ option:

NikoNeugebauer_1-1663952458507.png

 

3. Select ‘Configuring or using failover groups’:

NikoNeugebauer_2-1663952458508.png

 

4. In the ‘Diagnostics’ section, pick a time and select Submit:

NikoNeugebauer_3-1663952574423.png

 

Once diagnostics are complete, you should see one of the insights that delivers you the answer.

 

If global peering is supported, you should see:

 

NikoNeugebauer_4-1663952574431.png

 

Otherwise, if global peering is NOT supported, you will see:

NikoNeugebauer_5-1663952574442.png

 

For more information, see Enable and optimize geo-replication traffic flow between the instances

1 Comment
Version history
Last update:
‎Sep 23 2022 10:30 AM
Updated by: