How can fix LongTermRetentionBackupInternalError

Youssef Yassa 25

I am trying to make a backup to Azure database Postgres SQL flexible server but it fails and gives me this error LongTermRetentionBackupInternalError I followed https://learn.microsoft.com/en-us/azure/backup/backup-azure-database-postgresql-flex but still give me same error can some one help me please?

Anderson Leite 10 Reputation points

2024-08-15T08:07:53.7233333+00:00

I'm facing the exact same issue, some support from MS would be nice
Koen de Jaeger | Finalist 5 Reputation points

2024-08-23T10:37:06.0666667+00:00

Same here , in region westeurope, when enabling high availability.
Pol Valverde 0 Reputation points

2024-08-28T10:21:39.1166667+00:00
Same here in region westeurope with High availability not enabled in my case
Karen Turner (Catalyst) 0 Reputation points

2024-09-03T01:01:17.18+00:00

I was getting this error.

I set the backup instance in the Azure console and it assigned the roles for me.

But then I redid it in Terraform using Azurerm resource and got it to allocate a system assigned identity and two roles one scoped for reader for the resource group, and one for long term backup for the flexible db server. And that fixed it for me.
Anderson Leite 10 Reputation points

2024-09-03T07:45:21.8333333+00:00
I also have the same roles to reader at RG and Long Term Backup to the server, but I'm unable to make this work. At server I have a UserAssigned identity.

@Karen Turner (Catalyst) how did you manage to add a system identity to the PSQL Flexible Server ? On TF resource page (https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/postgresql_flexible_server) it mentions the only possible value to this as UserAssigned:

An identity block supports the following:

type - (Required) Specifies the type of Managed Service Identity that should be configured on this PostgreSQL Flexible Server. The only possible value is UserAssigned.
Pol Valverde 0 Reputation points

2024-09-03T15:47:40.6933333+00:00

I have the backup set with a weekly policy, and it magically worked this week. Maybe someone at Azure fixed something? I'm not sure if you all are still encountering the same error.
Anderson Leite 10 Reputation points

2024-09-03T15:59:16.0766667+00:00

After @Pol Valverde comment, I went back to check my backup vaults which was in a failed status for PSQL Flexible Servers, and... It magically started to work since September 1st:
Anderson Leite 10 Reputation points

2024-09-26T07:51:31.8366667+00:00

Microsoft closed my ticket, informing the issue is solved at West Europe region (at least for PostgreSQL Flexible Servers)

1 answer

Anderson Leite 10

I raised a issue with Microsoft, this was the latest feedback from them:


Issue: Some Azure Backup customers may experience incomplete backup jobs and subsequent failures with the error UserErrorMaxConcurrentOperationLimitReached.

Impact: This issue is intermittently affecting multiple servers in West Europe region.

Root Cause: The problem arises due to a limitation in PostgreSQL – Flexible Servers, which allows only 10 parallel clone servers. As a result, multiple backup jobs are queued, and some are delayed for up to 2 days, causing the SAS Uri provided by Azure Backup to expire.

Next Steps:

•       PostgreSQL team is working to increase the parallel job count to handle the load in the affected regions through a configuration update.
•       Azure Backup team will increase the SAS URI timeout period.


Currently PostgreSQL and AzureBackup are working to implement the fixes for deployment in order to prevent this issue in the future.```

Share via

How can fix LongTermRetentionBackupInternalError

1 answer

Your answer