Introducing Pre-Migration Validations for Single Server to Flexible Server Migration tool

This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .

In March 2023, we announced the general availability of the Single to Flex migration tool. Since then, we have seen many successful migrations and over 10K+ single servers migrate to Azure Database for PostgreSQL – Flexible Server. 

 

After reviewing migrations, we noticed that pre-migration setup process can prove to be a formidable obstacle. More than a third of the attempted migrations failed due to setup issues. Networking hiccups, authentication issues, permissions problems are some of the common setup issues faced by many customers. Though many customers were able to fix these issues and run successful migrations, we felt the need to address this gap in the migration tool given the huge number of migration failures.  

 

To make customers’ migration experience smoother, more predictable, and less stressful, we're excited to introduce a game-changing feature: Pre-Migration Validation. This feature is designed to validate both the source and target servers, ensuring they are fully prepared for the migration journey that lies ahead. 

 

How does Pre-Migration Validation work? 

Pre-Migration Validation feature seamlessly integrates into the current migration experience on Azure Portal. Now, customers can choose to Validate/ Migrate/ Validate and Migrate to suit their unique migration needs.

pre-migration-validations.png

 

  • Validate - Checks your server and database readiness for migration to the target. 
  • Migrate - Skips validations and starts migrations. 
  • Validate and Migrate - Performs validation before triggering a migration. Migration gets triggered only if there are no validation failures. 

Pre-Migration Validation runs a validation rule set against source and target servers. For each validation rule the result can be Succeeded/Failed/Warning.  

  • Succeeded: The validation succeeded. 
  • Failed: The validation failed and is a blocker for migration. 
  • Warning: These are important reminders to keep in mind when planning the migration.

To learn more, refer to this link. Get started on the portal experience here. 

 

In the next couple of months, we'll be introducing a bunch of new validation rules that will dive deep into the customer's database to ensure it's more prepared than ever before. 

 

Reach out to us at AskAzureDBforPGS2F@microsoft.com for any questions related to migrations or Azure Database for PostgreSQL - Flexible Server.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.