first things first, Case # is 06398030.
We are noticing across different customers that it seems like that apparently, Backup Copy Jobs targeting an immutable Wasabi S3 bucket are simply taking too much time to process the VMs for the small amount of data being transferred. You can consider, for example, the screenshot below. Available upload bandwidth on the Veeam side is capped to 40 Mbps anytime:
==================================================

==================================================
It seems like that overall performance of these Backup Copy Jobs is kind of "slower" to an extent that either it takes a lot of time for these jobs to complete or these jobs exceed the allowed window and, as a result, Veeam Backup & Replication will automatically stop them.
I’m wondering whether we are not probably facing an issue here, but instead what we are observing is the nature of Backup Copy Jobs targeting an S3 bucket located in a Public Cloud and not on-prem, which depends on both network bandwidth constraints and load on the public cloud side at any given time. Is it correct to say that there is a heavier lifting on the Veeam side when using Backup Copy Jobs compared to a S3 bucket part of a SOBR ?
Any help on this matter will be greatly appreciated.
Thanks and Regards,
Massimiliano