Azure Database for PostgreSQL Flexible fails to backup — internal server error after accepted backup request

Erik Melton 0 Reputation points
2026-10-20T07:47:14.24+00:00

Problem description

I am experiencing failures in vaulted long-term retention (LTR) backups for my Azure Database for PostgreSQL flexible server. Although the backup request is accepted and the pre-backup step completes successfully, the backup fails after approximately 87 minutes with an InternalServerError, and the error indicates isUserError=false.

Environment

The issue involves Azure Database for PostgreSQL flexible server located in the norwayeast region, with vaulted long-term retention backup enabled through Azure Backup, triggered via Azure CLI.

What I've already tried

Based on the case details, I verified the permissions of the vault's managed identity, ensuring it has the 'PostgreSQL Flexible Server Backup Contributor' role on the server, and checked that the vault and server are in the same region and meet all supported requirements. I also reviewed server activity logs and metrics during the backup window, confirming no interruptions or high load that could cause the backup to timeout. Despite these efforts, the backup still fails after about 87 minutes with an internal server error.

Current status

I am seeking guidance on how to resolve this internal server error during the backup process and whether there are additional diagnostic steps or configurations I should check to ensure successful vaulted LTR backups for my PostgreSQL flexible server.

Azure Backup
Azure Backup

An Azure backup service that provides built-in management at scale.

0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest
  1. Zoha Fatima 675 Reputation points
    2026-10-21T18:51:55.01+00:00

    Hi Erik,

    Since the backup request is accepted but fails after approximately 87 minutes with InternalServerError and isUserError=false, this suggests a possible Azure Backup service-side issue.

    As you have already verified permissions, regional compatibility, and server performance, I recommend checking the following:

    Review the failed backup job details and Backup Vault diagnostic logs for additional error information.

    Check Azure Service Health for any backup-related incidents in Norway East.

    Verify that no network restrictions or recent configuration changes are affecting the backup.

    Retry the backup once to determine whether the failure is temporary.

    If the issue persists, I recommend opening an Azure Support case with the backup job ID, correlation ID, failure timestamp, and error details. Microsoft's Backup engineering team can investigate the backend logs to identify the cause.

    Thank you, and feel free to respond back for more assistance.

    Was this answer helpful?

    0 comments

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.