Network Traffic throttling not applied after upgrade to 12.3.1.1139

[utleyab]

I have noticed that the Network Traffic throttling rules that are built in to Veeam B&R console are not applying.

While testing a server migration for a Veeam console, I was editing the Network Throttling rules to have the new source IP address of the new server, and when I went to verify the throttling was applying, I noticed that it wasn't. After performing a few tests to verify, it seems that none of the throttling rules are applying.

I've performed a few tests to make sure that it's not the target IP range that's the issue. We use Wasabi at location us-east-01 and while this doesn't have a specific set of IP rages documented, they are always within the constraints of 38.27.106.1-.255. On servers that work, this is the target range that they are set to, and it's always worked for the throttling of the job. I've verified that it does not work when the target IP range is set to all public IP addresses, set to the Wasabi range, or when using the built-in Internet rule that comes default on Veeam B&R console.

I've also performed the same tests on Veeam servers that are version 12.2.0.334 and it's confirmed that the network traffic throttling works on these devices. It seems that it's version 12.3.1.1139 that's the biggest commonality. I haven't tested on version 12.3.0.310 just yet - so no conclusion as to whether or not I've seen that on that one. I've checked multiple different clients, and it seems that the commonality between the ones that are not applying is the version number.

I do have a support case open (Case #07678129), but I wanted to check to see if anyone else has also experienced this issue.

Thanks!

[utleyab]

It is worth noting that the one client we have on version 12.3.0.310 seems to have its network traffic throttling rules working.

[veremin]

In general, network throttling rules only work between backup components (i.e., repositories, gateway servers, and so on - all components that carry Veeam data mover). They do not apply if you simply specify IP addresses or a list of them without ensuring that backup components are present in the specified ranges.

The only exception is the so-called Internet throttling rule, which manages traffic transferred through public networks.

Perhaps the difference between the two installations is that the Internet traffic rule is configured on one installation and not the other. Or, in one case, the object storage repository has a gateway server set up that is located close to Wasabi, while in the other, it does not.

Thanks!

[utleyab]

Even so, I've tested the Internet throttling rule as well, and that doesn't apply either.

[veremin]

In that case, I'm afraid we've exhausted the limit of assumptions, and it's best for you to continue working with the support engineer.

They will review the debug logs and your infrastructure to determine what might have gone wrong.

Thanks!

[9onzalo7]

Do you have any update/news on this case?