Job intermittently failing after V13 upgrade

[talanx]

I have 8 locations, each with a Scale-out Repository (Synology-NFS/Azure) each with their own local proxy.
Since my V13 upgrade, my Vmware backup jobs all intermittently fail with a cryptic "Time is out" error.
In Veeam Enterprise Manager, I can see the failures started on 12/15/25, the V13 upgrade was completed on 12/12/25.
None of these failures or anything close to them in logs before that date.
I didn't notice it at first, since Veeam does multiple retries, and it works on a retry or two.
Once I looked closer, it's also happening on the Scale-out Offload jobs to Azure, usually fails one or twice, then works fine.
Case # 07979563 opened on Feb 5th, and is getting nowhere.
We have restricted the number of jobs that can run at the same, uninstalled and reinstalled the proxies, added new proxies.
Single nightly backup job with multiple VM's in it.
I am still getting intermittent failures.

It could just be me, but Veeam support has taken a massive nosedive in the last few cases I have worked on.
I have opened 69 cases with Veeam in my history and have never run into this until the last few months.

I also dropped this case into the proper forum, just having here to show I am having issues with more than one:
My other case that is stuck was opened as a NAS backups taking a long time. Case # 07951608 opened 1/14/26.
I was backing up SMB files shares from a NAS (a Netapp) not realizing there was a better way to do it.
Support had me change my jobs from backing up from the SMB files shares to use the Netapp Native file tracking and backing up thru the Netapp so they would back faster.
The problem is, support can't get it to work.
We have created a new account on Netapp just for the file share back-ups working with support following the documentation, but it fails with permission issues. They are giving up and telling me I need to talk to Netapp.

Oh, and both cases have been escalated to managers and to my Veeam rep.

A disappointed customer.

[karsten123]

check fw ports and kb1999.
what are the hardware specs of your VBR?

[talanx]

No firewalls, VMware hosts, proxy, Synology on the same subnet/vlan (except going out to Azure).
No AV exclusions, running an EDR agent, not a traditional AV, worked fine in previous versions of Veeam, sounds like something to try.
EDR is not triggering any alerts on the proxies or VBR.
VBR - 8 CPUs/16 GB ram