more throttling and high cpu load after update to version 8.1.0.3503 P20250224

[sandsturm]

Hi
We have one VBO server and two proxy servers attached. One of these proxy hosts has quite a high cpu load after upgrading (constantly between 85 and 95%, but never a flatline on 100% (hit the ceiling)). Its just one of the proxies and I see this behavior only after the upgrade to latest patchlevel.
I updated to latest version 8.1.0.3503 P20250224. I can see a lot of jobs with the status: Objects waiting for processing.... I could'nt see that behavior before installing the newest patch.

I checked the logs on this affected proxy server and see a lot of the following entries:

- Microsoft Graph error: The request has been throtteled (code: activityLimitReached)
- Throtteled by organisation <orgID> reason: ThrotteledForPeriod....

Was something changed with the latest patch regarding the throttling behavior?

I'm not able to get all backupjobs done in the defined backupwindow (during night). Before the patch, this was never an issue....

I can create a support case, but thought to post it here in the forum hoping that someone else has the same experience and can help....

thx,
sandsturm

[mjr.epicfail]

Hi Sandsturm,

I think its best to create a supportcase for this, this is very hard to check without logs.

[Polina]

Hi sandsturm,

There were no specific changes for throttling in the latest patch.
But the v8 version overall has a general difference compared to previous versions - all SharePoint requests are not sent with the RateLimit headers. Based on these headers, Microsoft returns to the application their recommendations on wait time in case of throttling.

[t7MevELx0]

We're seeing the same issue — version 8.1.0.x is using an extremely high amount of CPU. It's overwhelming an entire Proxmox VE host with Platinum processors. I suspect it's related to the copy jobs that have been stuck in a "running" state since January 28th. I'm still waiting on a fix from Veeam support.

This high CPU usage only happens when copy jobs are running. When the environment is only running backup jobs (with no copy jobs), CPU usage stays near zero and everything performs well.

Maybe 8.1.1 will fix everything...