Processing of OneDrive very slow

[Tijz]

Hi all,

We have been running VBO for a couple of weeks now. I'm currently still testing with one organization consisting of about 44 users and 350GB data. But still the job runs for more than 7 hours every night, although there's not much new data.
Like last night, the job ran for 7h18m and only backed up 856MB of new data. The problem seems to be with a couple of onedrive objects. Every night, VBO takes about 5 to 6 hours to process the same 3 or 4 OneDrive objects.

What could be the cause of this?
The job reports "Target" as the bottleneck, but looking at the proxy/repository server I see no high load. CPU is at 2% and memory at 4.6GB. The VM is configured with 4 vCPU and 8GB RAM. (I know 8GB is the minimum, but considering only 4.6 is used in total I figured this should be fine for now). We use a NAS as backend, which is directly connected through windows iSCSI initiator and is backed by a RAID10 of 10 x 7200 disks. We formatted the volume with ReFS. Latency to this device as reported by windows resource monitor is very good (like 2ms).

Is this behaviour to be expected, or is there something to troubleshoot or improve in our setup

Regards, Tijs

[Tijz]

I created a support ticket for this: 03298215

Our logs are full of these:

23-11-2018 11:18:32 32 (4952) Error: The remote server returned an error: (429).
23-11-2018 11:18:32 32 (4952) Warning: Web request failed
23-11-2018 11:18:32 32 (4952) Unable to process request. Server cannot service the request
23-11-2018 11:18:32 32 (4952) Waiting before next processing attempt: 00:04:00...
23-11-2018 11:18:32 34 (504) Trying to resume...
23-11-2018 11:18:32 54 (2996) Trying to resume...
23-11-2018 11:18:32 26 (5632) Trying to resume...
23-11-2018 11:18:32 30 (348) Trying to resume...
23-11-2018 11:18:32 28 (4684) Web error occurred: ProtocolError
23-11-2018 11:18:32 28 (4684) Error: The remote server returned an error: (429).

[Polina]

Hi Mattijs,

Thank you for sharing the log details. This looks like a known issue and our support should be able to assist you by providing a hotfix.

I'd appreciate if you could get back with the results of the investigation. Thanks!

[heliosmedcomms]

As an aside, is Veeam Backup for Microsoft Office 365 a very new product? I'm currently at the start of a trial with iland and the whole restore process seems incredibly slow. I know that it's limited by the speed of the internet connection that you are running the Veeam Explorer on, but the OneDrive client can upload/download far faster than Veeam is able to restore - like 20 times faster.

[nielsengelen]

Rob, the product isn't that 'new' however OneDrive and SharePoint support were only added 6-7 months ago. If you are seeing slow processing it could be useful to contact support (which you already did via iLand reading your other thread) and let them analyze and fine tune where needed to improve this. Speed is always reliant on the connection and the amount of concurrent connections ongoing however 20 times difference looks like there is something we can adjust to speed it up.

[heliosmedcomms]

I'm waiting for iland to get back to me. IMO to have to install Veeam console and the Explorers on our own equipment - and thus a the mercy of our own internet connection to restore files, is a flaw in a cloud based offering. Not exactly a fault with Veeam because that's how it's designed but one kind of expected a web interface to restore files. Iland will have a much faster pipe to Microsoft Office 365 than us. PS. Whilst I've tacked on this thread, the slow restore we're getting is with a classic SharePoint site.

[Mike Resseler]

Hi Heliosmedcomms

The first issue, with the slow restore/ backup of the classic SP site probably means this is a site that has a lot of files. We are aware of this (In the end, OneDrive for Business is a classic SharePoint document library with a different "UI" on top of it) and we have a MSP fix available that makes it already faster (but we are working on speeding it up even more at this moment). The KB can be found here: https://www.veeam.com/kb2809

For the second, with the restore. We have full API support so service providers/ integrators/ ... can build this offering into their own portal. But we are seeing that not many are doing this, so we are thinking about a different approach. Nothing final in our thought process at the moment, let alone something we are developing