Backup slowness with Windows 10

[ericstar]

Hi,

We have tried to run a test of Office 365 Mailbox backup on latest Veeam 3.0 on different Windows machine, with below testing platform and duration of running the backup:

Windows Server 2012 R2 (VM) - Duration: 1hr 29mins
Windows 10 Pro (Physical Machine) - Duration: 8hrs 29mins

Testing Data: Office 365 with 100 mailbox and 4GB of data

Screenshots of platform hardware specification and the testing result for reference:
https://drive.google.com/file/d/12Wrwsj ... sp=sharing

Any clues on the slowness and incompleteness of data backup on physical Windows 10 Vs. Win Server VM?

Thanks.

[ejenner]

It should tell you what the bottleneck is in the 'Action' section at the bottom of the screen (with the job highlighted in the top half)

An example from one of mine: 02/07/2019 18:13:37 :: Load: Source 99% > Proxy 17% > Network 17% > Target 0%

From that you can clearly see the speed of the backup is controlled by the rate at which it can draw the data out of the source machine.

What do you get if you compare both of your jobs... or is that line not available for the o365 backup?

[ericstar]

Yes. From what I've seen the bottleneck was indicated as from "Source" in both jobs.

There seems to be no highlights of percentage breakdown in-line in the "Action" section, as per your example.

[ejenner]

As you've ruled out hardware specification as the cause (which is reasonable to do) maybe you're looking for some throttling which is applied somewhere.

I'm not hugely familiar with the o365 platform as I'm not responsible for it at our organization. But the kind of thing you might be looking for is a setting which will treat a connection from a server differently to a connection from a desktop? Or perhaps there's a time-related throttle that applies which chokes the connection during particular hours of the day.

[Polina]

Hi Eric,

The OS type should not be the case, and from your screenshots, the slowness could be a result of throttling on the source site.

What makes you think that one of the backups was incomplete? Both jobs run with a "success" state, which means that all data was fully processed.

Do you a support case opened?

[ericstar]

Hi Polina,

Realized the Veeam Backup for Office 365 has just release and it's great to know that it offers a solution of reducing throttling and thus improving backup performance.

Can I ask if you could share some insights as to how big the size of backup data and/or how powerful the backup machine we need in order to observe an obvious improvement in the backup speed? Would the improvement more prominent in the backup of OneDrive data, or SharePoint sites? Thank you.

[Polina]

Hi Eric,

The speed improvements apply specifically to SharePoint/OneDrive backups and can be achieved by adding a pool of auxiliary backup accounts (8 at least as suggested here), which help to distribute the load and prevent the "overheating" of SharePoint resources. There's no need to increase the compute/RAM on the VBO server; the system requirements didn't change.

Thanks!

[eirajeremy]

Hi,

We have tried to run a test of Office 365 Mailbox backup on latest Veeam 3.0 on different Windows machine, with below testing platform and duration of running the backup:

Windows Server 2012 R2 (VM) - Duration: 1hr 29mins
Windows 10 Pro (Physical Machine) - Duration: 8hrs 29mins

Testing Data: Office 365 with 100 mailbox and 4GB of data

Screenshots of platform hardware specification and the testing result for reference:
https://drive.google.com/file/d/12Wrwsj ... sp=sharing iq test free

Any clues on the slowness and incompleteness of data backup on physical Windows 10 Vs. Win Server VM?

Thanks.

It looks like you're experiencing significant backup slowness on Windows 10 compared to Windows Server 2012 R2. This could be due to several factors, such as system resource limitations, network configuration, or differences in how the operating systems handle I/O operations. Make sure to check the performance settings on your Windows 10 machine and ensure that there are no background processes consuming resources during the backup. Additionally, consider testing the backup with a wired connection if you're using Wi-Fi. Good luck!