Yep have seen that, can you check the number of network ports that are consumed on the VBR server, if in doubt run the below:
netstat -abno > C:\<Directory>\<filename.txt>
Sorry for double posting, after adding the code the page wouldn’t let change my formatting back from code…
I had this whereby ports were being exhausted on the VBR server to the repositories and proxies.
In one example I had AV issues that was breaking the communication down and forcing Veeam to set up additional listening ports & processes.
In another example I discovered a load of backup repositories misconfigured to not have any limit for concurrent tasks, and then backup copy jobs utilising them, if you don’t have a limit set then it’s 500 task concurrency, per repository, so this generated thousands of sessions of copying data, each needing VBR to orchestrate the process.
@MicoolPaul Thank you for this quick response ! I suspected the number of parallel tasks, this number is well configured on the repository
But I will ask to check again and run your cmd.