Windows SQL Servers Fail to Backup to Blob All other servers succeed

[damian.norton]

Case #04590600
SQL servers are around 2.3 TB and backups run 12 hours or more but eventually fail with the Unexpected error below.
I've tried creating a new job, new repository, modified the policy priority all to no avail.
Smaller Windows VMs without SQL succeed daily as expected.
Additional Details: We are using a single policy per VM and backing up to Azure Blob storage container as the repository.
I've created individual polices and individual repositories for my larger VMs that keep failing. Most recently received these errors:
Repository backup of [server2] has failed (An unexpected error, trace ID: c547a28c-3523-4084-9c8d-a9ab4217b9a7)
Repository backup of [server1] has failed (An unexpected error, trace ID: 981b5865-9b21-4c13-b069-73b466253fe5)

Any suggestions would be greatly appreciated.

[nielsengelen]

Hi Damian,

This is one of those issues which will require insight from support (most likely a remote session and log deep diving) to understand what is causing it. I'm not aware of other customers facing the same issue so hopefully, support can shed some light quickly. Can u create a case and let us know the case ID?