cannot restore database from automated backup

Question

Azure Database for PostgreSQL flexible server with a backup 14 retention period. We get an "InternalServerError" when trying to restore. The Quota appears to be 13% current usage. Errors:

An unexpected error occured while processing the request.

Tracking ID: '857d7205-729d-4942-80e2-c33c1a637791' (Code:

InternalServerError)

The resource write operation failed to complete successfully, because it reached terminal provisioning

state 'Failed'. (Code: ResourceDeploymentFailure, Target:

/subscriptions/xxxxxxxxx/resourceGroups/XXXXXXX/providers/Microsoft.DBforPostgreSQL/flexibleServers/XXXXX-db-2025-09-29-6)

Answer 1

Turns out the restore worked fine by changing the 'availability zone' in the server details (FYI - if someone else sees the same issue).

Answer 2

Hi Tech Admin •,

Greetings!!

It sounds like you're having a tough time restoring your Azure Database for PostgreSQL flexible server from an automated backup and running into an "InternalServerError." Here are a few steps to troubleshoot this issue:

1. Check Service Status: First, make sure there are no ongoing service issues in the Azure region where your PostgreSQL server is hosted. You can check the Azure Service Health for any disturbances.
2. Permissions: Ensure that you have the right permissions to access the backup and perform the restore. You should be at least a member of the Contributor role for the resource group containing your database.
3. Validate Backup Settings:
   • Review your backup retention period settings to ensure backups are still available within the retention window you configured.
   • Check if there's sufficient capacity in the storage account associated with your PostgreSQL server.
4. Troubleshoot Quota Issues: With only 13% usage, quota issues typically shouldn’t arise; however, check your resource usage; if your database is reaching its provisioned limit or if storage is exhausted, further operations may fail.
5. Review Logs: If possible, check any log files or audit logs for more specific errors that might indicate what’s causing the provisioning to fail.
6. Retry the Restore: Sometimes a simple retry works, so after checking everything, try the restore operation again.

If the above steps are not resolved your issue, please share the requested details in Private message.

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