Splitting Teams job into smaller jobs

[dotdk]

Hi Forum.

So we have a customer that is creating many new teams lately, and will continue to do so in the future.

Today we are handling all their teams by selecting their organization and then selected "Teams" to process, so that all new Teams are automatically being included whenever the backup job runs.

Teams job have passed 100.000 objects when running, and we sometimes see a warning "some objects were not enumerated" meaning that not all teams were discovered, so our backup is incomplete. This also means with such a hight amount of Teams/objects the backup job takes multiple days to complete.

Does anyone have any suggestions on how to automatically split the Teams backup job into multiple jobs and still automatically capture all new created teams?


Currently the setup is like this:

We have a dedicated proxy to handle the Teams job, and data is being written to an ObjectStorage repository.
Ideally it would be great to split the jobs into backup jobs containing for example 50000 objects and then creating a new job when object 50001 appears.

I seem to recall some PowerShell command, that could check if a team/object was in a existing job something like "-notinjob" but I'm unable to find it again.

Has anyone else dealt with a customer with a very high number of Teams, SharePoint ... leading to massive amounts of object ?

[Mildur]

Hi Thomas

Our recommended job/proxy limits are listed here:
https://bp.veeam.com/vb365/guide/design/maxconfig.html

We recommend 20'000 per proxy server. But you are protecting already 100'000 objects (1 Team counts as 2-3 objects: Teams files, Teams settings, Teams Chats). For that environment we would recommend to have 3-4 proxy server.

Currently the setup is like this:
We have a dedicated proxy to handle the Teams job, and data is being written to an ObjectStorage repository.
Ideally it would be great to split the jobs into backup jobs containing for example 50000 objects and then creating a new job when object 50001 appears.

I recommend to wait for our upcoming version 8 before completely changing your design (ETA Q3 2024).
Version 8 will allow you to create proxy pools and Linux proxies. Instead of splitting your Teams backup in multiple backup jobs, you will be able to have a single job and multiple Proxy server. That will be easier than using PowerShell scripts to manage job splitting.

My suggestion when Version 8 will arrive:
1. Update to v8
2. add 2-3 new Linux Proxy server (the job could even use free resources of other proxies if they are not processing any other jobs)
3. Continue with a single backup job and monitor the job sessions

Best,
Fabian

[dotdk]

Hi Fabian

I was hoping for something like that, as we have 12 Proxies in this customers environment, so there should be plenty of extra resources for when v8 arrives.

We will and see. Thanks