1 Share Point site backup extremely slow..

[raywu]

I have setup a backup task backup 100+ SharePoint sites, most sites are -100MB less and some of sites have few GBs data.
those above sites are backup fine except one huge site (Document Library) have 300GB having issue

I tried to setup backup task particular for this huge site, the read/write rate never hit 1MB/s, 1 & half hr only transferred 12MB data.
tried below method adjust setting but no help
https://www.reddit.com/r/Veeam/comments ... t/gafgs14/

no server performance issue CPU/network usage is very low, internet speed is fine hitting 900Mbps
The SharePoint Site is accessible
Veeam app ver: 6.0.0.400

Any suggestion to troubleshoot this slow backup issue?
#05539684

[HannesK]

Hello,
and welcome to the forums.

The first thing to troubleshoot I would do: updating to the latest product version. Auxiliary accounts probably don't work anymore, yes.

Best regards,
Hannes

[Mildur]

Hi

Additionally to what Hannes has suggested (updating to the latest version), you can check if you got throttled by Microsoft:
https://bp.veeam.com/vb365/guide/operat ... throttling

Code: Select all

cd C:\ProgramData\Veeam\Backup365\Logs
select-string "throttled [^0]" *

Auxiliary backup accounts can help in case you are getting throttled. They can be used if you are still using asic authentication (if so, please switch to modern-only authentication --> Basic Auth deprecated by microsoft).
With modern-only authentication, we don't recommend to add multiple backup applications to overcome throttling. Too many of these can lead to even slower processing. This function will be deprecated in a future version.

Thanks
Fabian

[raywu]

Hi Hannes

I ran the update check my version is most up to date v6.0.0.400
I ran the PS check throttling

Veeam.Archiver.Proxy_2022_08_06_16_48_14.log:45347:[05.10.2022 16:59:40] 171 (3572)
2a3f5214-3241-4a4c-b1d9-edee95f588ff: requests 2407, throttled 1
Veeam.Archiver.Proxy_2022_08_06_16_48_14.log:45364:[05.10.2022 16:59:40] 171 (3572)
890945bb-54ec-432e-8643-36fbddc484a0: requests 291, throttled 1
Veeam.Archiver.Proxy_2022_08_06_16_48_14.log:45383:[05.10.2022 16:59:40] 171 (3572)
4735d0cd-1ed2-46f9-97db-859f248b95e6: requests 2415, throttled 1
Veeam.Archiver.Proxy_2022_08_06_16_48_14.log:46110:[05.10.2022 22:10:19] 148 (4436)
ee13e1d3-fed3-4d12-acf0-6cc5b2b6cfd8: requests 2548, throttled 3
Veeam.Archiver.Proxy_2022_08_06_16_48_14.log:46133:[05.10.2022 22:10:19] 148 (4436)
6f37c920-5ee9-483a-9e74-16635801173f: requests 1983, throttled 1

seem not many throttled...
I always selected modern-only authentication for the backup account access O365. The Account side is fine as same AD account can run SharePoint backup for 99% of sites without any issue, except this site hv 300GB data it take ages to read data.
Duration is 14:39min and showing transferred data is 118MB

I ran another speed test copy 10 GB single file to SharePoint same site it finish in 10 mins, I dont think the speed issue is on Microsoft side..

[Mildur]

You have to update from the iso file. The update server doesn‘t push it over the update button.
I provided the link with the most current builds.

This is the most current one:
https://www.veeam.com/kb4347


Thank you
Fabian

[raywu]

Hi Fabian

thx for the iso file i managed to upgrade Veeam for Microsoft 365 to the latest version.
However the backup job still no going well i have setup a test backup task for 320GB SharePoint site, now the duration is 10 hrs 53 mins and transferred is 120MB
Read rate is 204kb/s, randomly drop down to 1xxkb/s i dont see it is reading file from SharePoint..

Ray

[Mike Resseler]

Hi Raywu, I noticed the case is closed but it seems it isn't solved yet. Any reason why the case is closed?

[raywu]

I ran another backup job particular for the problem SharePoint site
it completed with transferred data 254.5MB with duration 13 hrs

I can direct copy 10 GB single file on SharePoint web & download it within 15mins transfer time so my network is ok

Any further suggestion?

[raywu]

Hi mark

I havent receive any notice from Veeam about my case update ?! duno why it set to resolved as it is not ..

[Mildur]

Hi Raywu

It seems that the case was closed because there was no answer from the contact mail address from your side.
There was an Out of Office message from your colleague with a new contact mail address, but unfortunately it wasn't seen by our support system.

I talked to our support and a new case is required with new logs. The case from August and the logs are already too old to be reopened. Could you please open a new case and upload new logs? You can reference to your old support case (05539684). Please provide us also with the new case number.

Thank you very much
Fabian

[Johan M]

Hi Raywu

I had something simular with 1 site that ran for 100+ hours.

I have these 2 support tickets on it since it happened again with a new update
Case #05506383 - first case
Case #05605506 - second case

The first case we had Veeam change some items in the Proxy.xml file. I cant really explain more than this.

On the second case we had our customer change a setting in his M365 https://learn.microsoft.com/en-us/share ... -threshold and https://support.microsoft.com/en-us/off ... 4122f07c59
it has something to do with the view - What type of experience (view) is used on this site, modern or classic?
By default, the list view threshold is configured at 5,000 items, do they use default value ?

[raywu]

Hi Johan

Thx for the tips, the first one proxy.xml i dont think need to change anything in this file, as other sites with smaller document library 10GB less they are backup fine.
second one is interesting, i always applied modern view for all SharePoint sites, I compared the problem sites and good site config they are mostly same
I am trying to setup another generic O365 backup account for Veeam 365 backup test it out, since veeam support went silent now...

[Mildur]

As already explained by me, veeam support closed the case a few weeks ago because there was no answer from your colleague. Unfortunately, the automated out of office from your colleague was not processed by our system so our support wasn‘t aware of his longer absence.

A new case is required. Please provide the number with us.


Thank you
Fabian

[raywu]

Hi fabian

case opened for this issue with logs attached
Case #05676235

[Mildur]

Thank you.
I see you are already yin talk with our support engineer.
Let's wait for the extended debug logs to see what the next steps are.

Thanks
Fabian