Unable to Throttle a copy of backup

[Henrik.Grevelund]

Hi There,

Got a bit sad when i found out that throttle didnt apply to "Copy Backup" and "Move backup"
Why is this the only thing where the throttle rules doesn't apply ?

I had to import some backup from a old installation. First i found out that imported backup didn't get offloaded to the capacity tier(Case # 08073869)
So i had to create another bucket, and copy the backup. But the copy killed the customers internet connection.

Could we please get this fixed ?

I understand that the documentation says its only between veeam components the throttle works. But it does work with offload, even though its send directly from the repository server.
I my case i tried to use the VBR server as gateway, which then forced the traffic to go from the repository server to the VBR server, so between Veeam components. no luck.

Case # 08092088 - Unable to Throttle a copy of imported backup

[BenjaminPetersen]

According to the official docs, network traffic throttling does not apply to the backup copy or the move backup operations. This limit exists because traffic throttling in VBR is designed to control data transfer between Veeam components during normal job processing.

https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

Move and copy functions are considered data maintenance and they fall outside the throttling. That is why you see the rules being observed for SOBRs, they fall within the function of the transport channels that follow the rules

The best bet if this is something that you need monitored is to set up a QoS rule on the network side, that way if it does not fall into the Veeam Throttling rules it will not violate what you expect to/from this type of operation.