Throttling does not always work

[tiaccadi]

Hello,

my throttling settings reduce available bandwidth (100 KB/s) during the day (08:00 to 19:00), in order to have low impact on WAN links

If I start a job in that window (e.g. 10:00), bandwidth throttling is applied correctly. The job goes on for 9 hours at 100 KB/s. Once reached 19:00, the throttling switches off and the job goes on at full bandwidth (1 MB/s) for 13 hours

And here comes the issue: the next day in the morning (at 08:00) the throttling seems to not apply anymore, and bandwidth isn't limited

This happens both if the job is the same or if it's a new one (the next VM in the scheduler)
And moreover, it happens both if I check "Use multiple upload streams for job" or if I don't

Last information: I've already updated Veeam B&R to 7.0 R2

What could it be the problem?

[foggy]

There is a known issue regarding throttling rules that seems to cover your case, will be addressed in the next product update. Sorry for inconvenience.

As a workaround, you can try to create additional throttling rule with high bandwidth and all-time allow interval (24h), it will have lower priority but probably will cause the correct behavior (didn't test it).

[tiaccadi]

I'll try that and I'll post some feedback
Thank you very much!

[lobo519]

What exactly is the situation that causes the issue?

Did this work for you? I think I am having a similar issue Case # 00512944.

Any time frame on the next release?

[Gostev]

This month.

[veremin]

Did this work for you?

What about setting an additional throttling rule, as recommended by Alexander? Have you tried to do it? I know it's nothing but a workaround, though, it still might be helpful for you.

Thanks.

[lobo519]

Gostev - Correct me if I am wrong but Throttling rules are set globally correct? If the Poxy IP falls within the range it applies correct?

Also - I do not need to created separate rules for inbound and outbound traffic - One rule will work for both directions?

[foggy]

Though I'm not Gostev, but yes, throttling rules are set globally within Veeam B&R server. If a pair of IPs satisfies some rule, this rule will be applied to connection between them.

[lobo519]

haha - thanks guys - I will try adding the second rule

side note - Please take a look at this case. The rep is giving out incorrect information as confirmed by Foggy. This is a perfect example of why people ask questions here first (its where the experts are!)

[foggy]

Probably he was confused by the fact that the rules list is available in several places. The one available while adding proxy servers indeed contains only rules that are applicable to the proxy being added (no sense to display other rules here), however the rule created at this step gets into the global list of rules available on the main product menu.

[lobo519]

I agree with you but even after I pointed out he was incorrect he still insisted. Also he is "confused" about the direction of the rules.

I'm not trying to cause a big debate here but its disappointing when support gives these responses. This seems like basic functionality everyone should be well aware of.

[lobo519]

Adding the additional rule doesn't appear to have worked.

[Ben Milligan]

Hi there - Ben from tech support here. I reviewed your case and it does appear you are indeed running into a known bug. We have advised the engineer working your case on this, as it was a clear oversight on our end. You'll be getting the hotfix and instructions today.

PS: It is also planned to be in the next cumulative patch.

[lobo519]

Thanks for your assistance!!

[lobo519]

Well this patch didn't fix the issue. But after working with support more, it was determined that I needed to setup the throttling rule for the ISCSI network as well (I'm using direct SAN access).

After adding the same rule with the source IP range of the ISCSI network - throttling appears to be working.

[Ben Milligan]

Thanks for the heads up on that, I'm glad its working for you now.