Share via

Unable to migrate Postgres Single Server

Rakshak Shrestha 20 Reputation points
2025-05-10T02:51:16.02+00:00

Azure Postgres Single Server has been disabled automatically.

The message in the resource page displays "The last migration attempt didn't work or was cancelled. We'll reschedule the automatic migration soon."

When I try to manually start the migration, I'm not able to connect to the source database at all.

We really need a way to either backup or migrate this database into an appropriate server.

Azure Database for PostgreSQL
Accepted answer
  1. Saraswathi Devadula 2,260 Reputation points Microsoft External Staff Moderator
    2025-05-12T05:32:42.77+00:00

    Hi Rakshak Shrestha,

    I understand that you are unable to migrate Postgres Single Server due to some issue stated.

    User's image

    I would like to inform you that, we have enabled the PostgreSQL single server for the next 30 days to migrate it to the Flexible Server, this is not extendable.

    Use our migration service in Azure Database for PostgreSQL to simplify the migration experience. It provides both offline and online migration options.  https://learn.microsoft.com/en-us/azure/postgresql/migrate/migration-service/tutorial-migration-service-single-to-flexible

    Auto-migration option (offline mode only) can keep server name and DNS the same, so the application won’t need any connection string changes.

    Note: Public Access needs to be enabled for the Single Server, and CMK server can’t be created using auto-migration.

    I hope this information helps. Please do let us know if you have any further queries.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sina Salam 20,106 Reputation points Moderator
    2025-05-10T07:36:54.77+00:00

    Hello Rakshak Shrestha,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that you are unable to migrate Postgres Single Server due to some issue stated above.

    Regarding Microsoft Documents, the root cause might be linked to Connection Timeouts or Network Issues, permission, an/or service limitations.

    However, this is critical situation, try to check if the Source Server is permanently disabled, and if the server is still partially accessible you can use pg_dump via Azure Cloud Shell or a VM in the same VNet or try Azure CLI with the command below:

    pg_dump -h <source-server>.postgres.database.azure.com -U <admin-user> -d <database-name> -F c -f backup.dump

    To try exporting a backup.

    Also, if the server is completely inaccessible, and migration fails open a support ticket with Microsoft via Azure Portal or Priority Customer Support.

    Alternatively, if you had automated backups enabled then try to restore from Azure Backups.

    I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.