Throttling SOBR direct to Archive

[JaySt]

trying the 12.2 direct to archive tier feature.
pre-12.2 we tried the offload from performance tier to capacity tier (Azure blob storage) and this was honoring the throttling rules.
Now, when we try the same for direct archiving from performance tier to Azure Archive (archive tier), throttling does not seem to work.

is this expected behavior?

[Gostev]

No, I don't recall this being discussed or documented as a limitation so it's worth investigating with support.

Just to clarify, are you saying your "Internet" rule no longer applies?

At the very least it should be possible to throttle traffic between the Performance Tier extent and the archive repository gateways server, as this would be completely regular source and target datamovers couple to which Global Network Traffic Throttling rules apply.

[JaySt]

correct, the "internet" rule was not working anymore, when it wás working for offloading to capacity tier.
because a workarround is in place and i dont have frequent access to the environment, i dont think support will be involved anymore
workarround that was used involved creating a local Windows QoS policy using Gpedit.msc -> Computer configuration -> Windows Setttings -> Policy-Based QoS. We created a policy limiting all outbound traffic on 443. Seems to work fine, adjustments there are instant too.

We tried to a direct connection and a gateway connection, in both cases the internet rule was not limiting the traffic.
When looking at the documentation as it currently is (Page updated 5/17/2024) : https://helpcenter.veeam.com/docs/backu ... ml?ver=120
We think to interpret the page into saying -backups- to object storage (direct or through gateway) get throttled and also -offloading-. Because the archive process is probably different to -offloading- , perhaps it's not implemented yet? Archiving is not specifically mentioned (yet). pre-12.2, the helper appliances did the work, perhaps not needing throttling logic. 12.2 brings that handling(helper appliance processes) onprem to a local component and maybe throttling logic was not applied yet?
so far our reasoning...

[veremin]

Indeed, right after the release of version 12.2, we discovered the mentioned bug - the Internet throttling rule does not work in scenarios with Direct to Archive. Currently, we are planning to fix it in version 12.3. Thanks!

[Gostev]

How easy it is to create a hotfix @veremin?

[veremin]

I have talked with the R&D team, and they will recheck the mentioned bug soon and assess how difficult it will be to prepare a hotfix for it . I will update this topic once there is any news. Thanks!

[veremin]

@JaySt

The development team has taken another look at the bug and concluded that a hotfix can be fairly easily prepared for it. However, we would like the issue to go through the support team's hands first.

So, can I ask you to create a case with the support team and share the ticket number on the forum? We will then escalate it to the R&D team and provide you with the hotfix within the existing case (after a quick check to ensure it doesn't cause any other issues).

Thanks!

[JaySt]

I will try to do so! Will report back

[JaySt]

case #07402591

[veremin]

Thank you, I've passed it to the R&D team. Will let you know, if any further assistance is required.

[veremin]

According the support team, the ticket will soon be escalated for further review by the R&D team and for hotfix creation. Thanks!

[iDeNt_5]

Hi all,

Since I'm interested too in this thread on a Customer behalf, is there any news on the bug fix that prevents the throttling from working in the direct to Archive backup offload?

Thanks.

[veremin]

Hi, Matteo,

You're just in time - we have just recently implemented a hotfix and handed it over to the support team as part of this ticket (07402591).

If your client is experiencing the same issue, please ask them to open their own case and reference the information I mentioned above. After that, the hotfix will be shared with them.

Thanks!