Share via

My PostgreSQL single server disappeared after automatic migration?

Fabian Schmidt 50 Reputation points
2024-09-12T06:58:51.29+00:00

Hello, my Azure Database for PostgreSQL single server should have been migrated to Azure Database for PostgreSQL flexible server. The the automatic migration took over 1 week. The scheduled time for migration start was 9/4/2024. Yesterday the "old" Azure Database for PostgreSQL single server Resource just disappeared. I tried to search for it in my Resource Group and also tried to use the old link to the database server component which is shown a 404 now. And no "new" Azure Database for PostgreSQL flexible server can be found either? My services are still running and are connected to the database. I got 0 information or notification about this weird behavior? Is this normal? What should I do next?

Azure Database for PostgreSQL

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Fabian Schmidt 50 Reputation points
    2024-09-17T10:58:29.3433333+00:00

    After contacting MS support a service worker has checked and fixed the issue. Now my new flexible server is visible in my res group.

    2 people found this answer helpful.
    0 comments
  2. Bid Parcel 0 Reputation points
    2024-09-23T23:42:47.1366667+00:00

    Any update on this subject. I still cannot see my databses and this is impacting a lot all of our business, Please assist on this.

    0 comments
  3. Amira Bedhiafi 41,131 Reputation points Volunteer Moderator
    2024-09-12T21:26:54.5266667+00:00

    Here’s what you can do next:

    1. Check the Migration Status and Notifications:
      • Check Azure Service Health for any notices or warnings related to your resource group or PostgreSQL migration.
      • Look at the Activity Log in the Azure portal for any events related to your single server or the flexible server that might provide insights.
      • Also, review any emails or portal notifications from Azure about the migration process. Sometimes notifications can be overlooked.
    2. Verify Database Connections:
      • Since your services are still running and connected, check the connection strings or the configuration files in your services to determine where they are connecting.
      • This will give you clues about the new server’s address or any changes that happened during the migration.
    3. Search for Flexible Server Resources:
      • Make sure to search in the correct Subscription and Resource Group. Sometimes resources may end up in a different group than expected.
      • You can also try Azure CLI or PowerShell to list your PostgreSQL resources, in case there’s an issue with the portal display. 
             
     az postgres flexible-server list --resource-group <your-resource-group-name>

    As a precaution, consider taking database backups if possible, through your services or other connected tools, just in case something goes wrong while waiting for the resolution and try to contact Azure Support.

Your answer

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