An Azure backup service that provides built-in management at scale.
Azure Backup: Vaulted PostgreSQL Flexible Server Backup Stuck InProgress After Failed 7-Day Backup with InternalServerError
Problem description
I am experiencing an issue where the backup for my Azure Database for PostgreSQL Flexible Server in the UK South region is stuck in the 'InProgress' state. Previously, a scheduled 7-day backup started on November 6, 2026, and ran for about seven days before failing with an 'InternalServerError'. The subsequent backup job, initiated on November 13, 2026, remains stuck in the 'Trigger Backup' / 'InProgress' state. The server is currently shown as 'Ready', and the server's health, high availability, and storage usage appear normal. I have verified that the backup vault and backup instance have the appropriate roles assigned, and I have confirmed that recovery points are available up to May 29, 2026. No recent configuration changes or failovers have occurred around the time the issue started. I am seeking guidance on how to resolve this stuck backup job and whether any backend operations can be cleared without affecting existing recovery points.
Environment
Azure Backup vault protecting an Azure Database for PostgreSQL Flexible Server in UK South; workload is production; protection objects include one vault and one backup instance; server state is 'Ready'.
What I've already tried
I have verified the server health, HA status, storage usage, and backup roles. I checked the activity logs and confirmed no configuration changes, restarts, failovers, or scale operations occurred around the time the backup started failing. I also confirmed that recovery points up to May 29, 2026, are available and that the server and backup roles are correctly assigned. Additionally, I have not manually triggered any on-demand backups since the job is already stuck.
Current status
I am seeking assistance to investigate the backend operation associated with the failed backup on November 6 and the currently stuck job from November 13. Specifically, I want to know if the stuck backup process can be cleared without deleting the backup instance or impacting existing recovery points, and how to proceed with resolving the stuck job to ensure backups resume normally.