Sharepoint online throttling

[matteu]

Hello,

I would like to backup my sharepoint online but bandwith is incredibly low (some KB/s) and on the log I can see event 429 for microsoft throttling and my bottleneck is the source.
I use basic authentication with 6 account but nothing is better.

I use the latest version of the VBO365.

Is there a way to improve it ? I don't find anything on documentation or forum about it

Thanks

[Mildur]

Hi Matteu

Alex had a similar issue and he has resolved that with 32 or even more backup accounts. He has tested it with 128 Accounts.
I can see that in my environment too. We are using at the moment 15 backup Accounts for a 1 TB Sharepoint Site. Microsoft doesn‘t like the regular download of the data and is throttling our backup accounts many times.

post431405.html#p431405

[matteu]

Thanks one more time for your fast answer

Now I'm testing it on lab environment but I need to do it on 2TB sharepoint data.
That means I will have to create a lot of account right ?

[Mildur]

Yes, i think, at the moment it‘s the best workaround.
The accounts do need any license. They are free.
There is a script which will create the backup accounts for you:

For Backup Accounts (Basic Auth):
https://github.com/nielsengelen/veeam-p ... tor-v5.ps1

I don‘t know a script for backup application (modern auth).
For modern Auth Apps, only this permissions are needed to backup sharepoint and one drive:

https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=50

[matteu]

Thank you very much, I will try as soon as I can

[Mildur]

Your welcome.
Please give us a Feedback if more backup accounts will help with the speed

[karsten123]

The best and fastest way is, to do it with modern authentication only. The GUI will create the backup applications for you.
cheers

[matteu]

The issue is modern authentication doesn't support what basic authentication support.
https://www.veeam.com/kb3146

[karsten123]

maybe. but modern auth will be the only available method very soon.

[matteu]

Yes, in one year.
Microsoft annonced basic authentication will not work after october 2022
https://techcommunity.microsoft.com/t5/ ... -p/2772210
Maybe more improvment on modern authentication are comming before this date

[Mildur]

Veeam will definitely talk to their microsoft contacts and doing everything they can to get their software working with modern auth only. Microsoft needs to create APIs for some of the data to backup over modern auth only.

[matteu]

Result for my test:

Sharepoint 4900elements - 3Go



We can see auxiliary backup are necessary and performance are the same on this case between modern or basic.

[AlexHeylin]

Hi Matteu,

I'm glad my extensive updates to the other thread proved useful.

Thanks for posting your testing results. They confirm my intuition - Modern auth seems significantly slower unless throttling is completely absent.

It's worth pointing out that while @karsten123 is correct that the GUI will create additional backup applications for modern auth only setups - it won't do it automatically. I'm now setting up 32 backup accounts / backup applications as the bare minimum and routinely creating 128-300 even for small (0.5 - 5 TB) tenants.

Our largest tenant (and first VBO tenant) is still using legacy auth on a single account, and item based retention. However they're not using O365 for file storage yet. We're going to have to rebuild their backup config anyway because a well intentioned tech used "item based" retention (I think it was the default then) with "forever" retention policy (then set up NTFS deduplication - yes, I can hear you screaming!) and now amazingly the 16GB volume is full. I'm going to "strongly suggest" to the client team that they do not consider moving files to O365 for at least two years given MS making it so difficult to reliably back up.

[matteu]

Thanks for your answer and your help on this issue

Good luck for your next project

[AlexHeylin]

Just to add for completeness that I've recently found out the incremental backups of SP sites only use a single thread and this problem occurs regardless of throttling / resources. Support have confirmed this is what happens.
I think it also uses a single account / application until throttling causes a hard fail then after ~30 mins of retrying it changes account. For us these issues cause a much larger impact than throttling - and the only way to resolve it is for Veeam to rewrite their code. There's no config that affects this.
Check my other thread for details - and please comment on post431405.html that SP sites MUST use multiple threads per site.
Thanks

[matteu]

thanks for the news

[AlexHeylin]

Apparently I mean threads per LIST, not per Site... I've opened a specific enhancement request as I was advised to post436043.html#p436043 so please comment on that instead