Migration of Azure SQL Database Fails Using Resource Mover

Question

Why does my Azure SQL Database migration from one region to another using Azure Resource Mover not complete successfully?

PS - Based on common issues that we have seen from customers and other sources, we are posting these questions to help the Azure community

Answer 1

Greetings!

The issue you're encountering with the Azure SQL Database migration using the Azure Resource Mover tool occurs because the target resource group was set to a null value, causing the operation to remain in an "AssignmentPending" state. During our troubleshooting session, we reviewed your migration steps and identified that the migration does not complete due to downtime constraints and misconfiguration of the target server.

 As a solution, for scenarios where downtime is acceptable, Azure Resource Mover is a viable option. However, since you need minimal downtime, we recommend using Geo-Replication for the migration. Geo-Replication allows you to configure a secondary replica with minimal downtime, only during the failover process.

 Here are the steps to follow for Geo-Replication:

 1. Ensure that the database encryption configuration (TDE) is the same for both source and destination.

2. Create a Geo-Replication link for the database.
3. Once the secondary replica is synchronized, plan a maintenance window for the failover during off-peak hours to minimize impact.
4. Perform the failover, which typically takes about 4-7 seconds.
5. Update the connection strings in your application to point to the new server.

 

For detailed steps, refer to the following documentation:

• Move Azure SQL resources between regions with Azure Resource Mover
• Tutorial: Geo-replication & failover in Azure SQL Database

  

Please do not forget "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.

Regards

Geetha