Select Language:
This is a serious production problem that needs immediate attention.
Right now, I’m facing the same issue others have reported with Azure PostgreSQL Flexible Server. The server has been stuck in a Stopped / Starting state for hours, and I can’t restart it using the Azure portal or command line interface. Additionally, the Point-In-Time Recovery (PITR) and Fast Restore options are failing. Restoring from a different region is blocked due to subscription or regional restrictions. Although I can see automatic backups, I have no way to access or restore them.
This server holds several months’ worth of live production data. We didn’t set up any external backups, trusting Azure’s automatic backup services. At this point, it’s clear that this isn’t a misconfiguration or user error. It’s a service-level failure that leaves us without access to our critical data.
We need clear answers from Microsoft support now. Are the automatic backups still safe and intact? Can Microsoft perform an internal restore to a new server? What’s the official recovery plan when a server gets stuck like this and can’t be recovered? Why isn’t there a customer-facing way to export or access backups during such incidents?
This situation poses a high risk of data loss for our production environment and should be treated as a critical severity level (SEV-A). We’re requesting urgent intervention from Microsoft’s engineering team—not just links to documentation. Any guidance, escalation options, or confirmation about internal recovery steps will be greatly appreciated.
This is a vital issue that demands immediate action.
ChatGPT
Perplexity
Gemini AI
Grok AI
