Contradictory pieces of information in the documentation about Azure PostgreSQL Single Server to Flexible Server migration

Question

Hello, I want to migrate an Azure PostgreSQL Single Server to an Azure PostgreSQL Flexible Server.

When reading your documentation about how to use the Single Server to Flexible Server Migration Tool, I see that I should not enable geo-redundancy while migrating but only enable it after the migration is complete, with no downtime. (https://learn.microsoft.com/en-us/azure/postgresql/migrate/concepts-single-to-flexible#migration)

However, I also read in the documentation about Flexible Server Backup & Restore that it is possible to select geo-redundant backup storage only when creating the server. (https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-backup-restore#backup-redundancy-options)

As these two pieces of information contradict each other, could you tell me which is right, and how should I proceed with geo-redundancy activation while migrating ?

Thank you in advance for your answer.

Best regards. Alexandre

Answer 1

@Alexandre Thanks for bringing up this issue As a part of the best practice for migration, it is advised not to enable HA and geo backups since we would need to copy data and files across regions (in case of geo backup). But given the fact, that you can only enable geoback at the time of server creation, the possible workaround will be to do the following :

1. Create a flexible server without geo backup
2. Complete the migration
3. Take a PITR of this flexible server
4. While creating PITR, choose the option of geo backup
5. This PITR will now be the primary flexible server and connection strings of application can point to this.
6. Delete the flexible server used for migration We will update the document as well. I hope this information helps. Regards Geetha

Answer 2

Hello, The first documentation about the migration tool advises not to enable geo-redundancy for the source Single Server during migration. This is to avoid any potential issues or conflicts with the migration process. The second documentation about Flexible Server Backup & Restore is referring to enabling geo-redundant backup storage when creating a Flexible Server.

Here's how you should proceed with your migration and geo-redundancy activation:

1. Do not enable geo-redundancy on the source Single Server during the migration process.
2. When creating the target Flexible Server, enable geo-redundant backup storage during the creation process as mentioned in the Flexible Server Backup & Restore documentation.
3. Follow the migration steps provided in the documentation to migrate your data from the source Single Server to the target Flexible Server. Don't forget to mark the question as answered if it was helpfull for other users with same concerns to find the topic

Regards