Priority of Jobs

[dali@iae.nl]

Normally our MS365 Exchange Job has finished in 2 to 3 hours.
But when another job starts, for example a OneDrive Backup, the Exchange Job runs much slower an can take more than one day to complete.
Is there any trick to ensure the Exchange Job has more priority over other Jobs?

[Mildur]

Hi Dali

We don't have prioritization in our VB365 jobs.
May I ask how big your M365 tenant is? Depending on the size and amount of objects to protect it could make sense to use a second proxy server.

Another option is to open a support case if you think there are performance issues. Our customer support may recommend a way forward if Jobs are taking too long to finish.

Best,
Fabian

[dali@iae.nl]

The tenant is about 45TB.
At the moment I'm splitting the OneDrive Jobs in little portions and I have limited the number of threats. It seems to get better. I'll wait for the first new full's have been taken.

[Mildur]

Hi Da Li

I apologize for the late answer. I was out of office in the last 3 weeks.
Could you improve the performance? Initial backup jobs may always take more time.

Best,
Fabian

[dali@iae.nl]

Initial is still running, now about 31TB. But yes, with lesser Threats (16-24) for this initial it seems to get better than the standard 64.
I splitted in about 12 Jobs, with Dynamic AAD Groups assigned, for example first letter A or B and Member of O365.

[dali@iae.nl]

In the end all initial OneDrive backups are ready with the Proxy running on 16 threads. About 35TB took a lot of weeks to compleet. That's with the total splitted up in 14 separate jobs based on first names (tried to get 50-150 persons per job).
Changed the threads back to 64, auxiliary backup applications are still 4.
When I now start all 14 jobs together they will finish rapidly. No need to prioritize the jobs anymore. Case closed.

[Mildur]

Hi Da Li

Thanks for the update.

Best,
Fabian