Azure SQL MI how to stop sync from primary node to secondary node in failover group

Hi Li, Jindong,

Greetings!

To stop syncing data from the primary node to the secondary node during migration, you can temporarily remove the secondary node from the failover group.

Here’s how you can do it:

Remove the Secondary Node from the Failover Group: Use the Azure portal, PowerShell, or Azure CLI to remove the secondary node from the failover group. This will stop the data synchronization between the primary and secondary nodes.

Example PowerShell command:

Remove-AzSqlDatabaseFailoverGroup -ResourceGroupName "ResourceGroup" -ServerName "PrimaryServer" -FailoverGroupName "FailoverGroup"

For more information, please refer the document: https://learn.microsoft.com/en-us/powershell/module/az.sql/remove-azsqldatabasefailovergroup?view=azps-13.4.0

Operations for Secondary Node Before Adding Back to Failover Group.

• The secondary managed instance must be empty, without any user databases.
• Both the primary and secondary instances should be of the same service tier and have the same storage size.
• Ensure that the IP address range for the virtual network of the primary instance does not overlap with the address range of the virtual network for the secondary instance.
• Both instances must be in the same DNS zone. When creating the secondary instance, specify the primary instance's DNS zone ID.
• Ensure that Network Security Groups (NSG) rules for the subnets of both instances have open inbound and outbound TCP connections for port 5022 and port range 11000-11999.

For more information, please refer the document: https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/failover-group-configure-sql-mi?view=azuresql&tabs=azure-portal%2Cazure-portal-modify%2Cazure-powershell-manage

Adding the Secondary Node Back to the Failover Group:

Once the secondary node is ready, you can add it back to the failover group

Use the Azure portal or PowerShell to create the secondary instance with the appropriate configurations.

Example PowerShell command:

Add-AzSqlDatabaseFailoverGroup -ResourceGroupName "ResourceGroup" -ServerName "PrimaryServer" -PartnerServerName "SecondaryServer" -FailoverGroupName "FailoverGroup"

For more information, please refer the document: https://learn.microsoft.com/en-us/powershell/module/az.sql/add-azsqldatabasetofailovergroup?view=azps-13.4.0

I hope this information helps. Please do let us know if you have any further queries.

Hi Li, Jindong,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.