Edit

Share via

Premigration validation for the migrations service in Azure Database for PostgreSQL

APPLIES TO: Azure Database for PostgreSQL - Flexible Server

Premigration validation is a set of rules that involves assessing and verifying the readiness of a source database system for migration to Azure Database for PostgreSQL. This process identifies and addresses potential issues affecting the database's migration or post-migration operation.

How do you use the premigration validation feature?

You can migrate by using Azure portal or Azure CLI.

Using the Azure portal:

  1. Select your Azure Database for PostgreSQL flexible server.

  2. In the resource menu, select Migration.

    Screenshot of the Migration page.

  3. Select Create to go through a wizard-based series of tabs to perform a migration to a flexible server from on-premises or Azure VM.

    Screenshot of the Setup tab which appears after selecting Create in the Migration page.

  4. In Migration option, select Validate or Validate and migrate.

    Screenshot that shows the premigration option to start migration.

Premigration validation options

You can choose any of the following options:

  • Validate: Use this option to check your server and database readiness for migration to the target. This option won't start data migration and won't require any server downtime.
    • Plan your migrations better by performing premigration validations in advance to know the potential issues you might encounter while you perform migrations.
  • Validate and migrate: This option performs validations, and migration gets triggered if all checks are in the Succeeded or Warning state. Validation failures don't start the migration between source and target servers.

We recommend that you use premigration validations to identify issues before you run migrations. This technique helps you to plan your migrations better and avoid any surprises during the migration process.

  1. Choose the Validate option and run premigration validation on an advanced date of your planned migration.

  2. Analyze the output and take any remedial actions for any errors.

  3. Rerun step 1 until the validation is successful.

  4. Start the migration by using the Validate and migrate option on the planned date and time.

Validation states

After you run the Validate option, you see one of the following options:

  • Succeeded: No issues were found and you can plan for the migration.
  • Failed: Errors were found during validation, which can cause the migration to fail. Review the list of errors and their suggested workarounds. Take corrective measures before you plan the migration.
  • Warning: Warnings are informative messages you must remember while you plan the migration.

Related content