How to migrate Postgres Database from One Azure Entity to Another Azure Entity

Question

Hi,

We have a PostgreSQL flexible server hosted on Azure under the entity (abc.com). Due to some business changes, we need to migrate the PostgreSQL database from entity (abc.com) to entity (xyz.com).

Could you please suggest the best ways to perform this migration while ensuring zero downtime and zero error tolerance?

Thank you for your assistance.

Best regards,

Sasi K

Answer 1

Hello Sasi, Welcome to MS Q&A

To migrate a PostgreSQL database from one Azure entity to another while ensuring zero downtime and zero error tolerance,

1. Initial Preparation:
   • Assess the Current Setup: Review the current PostgreSQL flexible server configuration, including database size, performance metrics, and dependencies.
   • Plan the Migration: Define the migration strategy, including timelines, resources, and roles.
2. Set Up the Target Environment:
   • Create a New PostgreSQL Server: Set up a new PostgreSQL flexible server under the new entity (xyz.com) with the same configuration as the source server.
   • Configure Network and Security: Ensure that network settings, firewalls, and security groups are configured to allow seamless data transfer between the source and target servers.
3. Initial Data Transfer:
   • Base Copy: Perform an initial base copy of the database using tools like Azure Database Migration Service (DMS) or pg_dump/pg_restore. This creates a snapshot of the data to be used as the foundation for the migration.
   • Data Validation: Validate the initial data transfer by comparing row counts, database objects, and key application-related columns between the source and target databases.
4. Continuous Data Synchronization:
   • Set Up Replication: Use logical replication or tools like Azure DMS to continuously synchronize data changes from the source database to the target database. This ensures that the target database remains up-to-date with the source database.
   • Monitor Performance: Continuously monitor the performance of both the source and target databases to identify and address any potential issues early.
5. Cutover Window:
   • Schedule Cutover: Plan a cutover window during a period of low application traffic to minimize disruption.
   • Final Synchronization: Perform a final synchronization to ensure that all data changes are replicated to the target database.
   • Switch Application Connections: Update application configurations to point to the new PostgreSQL server under the new entity (xyz.com).
6. Post-Migration Validation:
   • Data Validation: Perform thorough data validation to ensure that the data in the target server is an exact copy of the source instance.
   • Application Testing: Conduct application testing to verify that all functionalities are working as expected with the new database.
7. Decommission the Source Environment:
   • Monitor Stability: Monitor the stability and performance of the new PostgreSQL server for a defined period.
   • Decommission Source Server: Once confirmed that the new server is stable and fully functional, decommission the source PostgreSQL server under the old entity (abc.com).

By following these steps, you can effectively migrate your PostgreSQL database with minimal disruption and high reliability.

References:

• Best practices for seamless migration into Azure Database for PostgreSQL

Please let us know if any further questions

Kindly accept if it works

Thanks

Deepanshu