We are still working with support on these cases and one of the common requests we get is "split the jobs".
For example splitting a large Teams job into multiple segments for easier trouble shooting and hey, it might actually be the reason for the slowdown.
But that is the worst thing for a service provider, because that means you cant just let the job run and there is no scheduler inside of Veeam to support this use case. You cannot use the normal scheduler for this, because if the jobs overlap it has the cascading effects of ruining all your backups that day.
One client has 35 security group jobs, with Mail/archive, Sites and Ondrive, about 2000 objects per group.
We have been told to split these into Exchange, OneDrive and Sites. 35 jobs split into 3 is 105 jobs which we then have to schedule somewhere and somehow.
If this is such a common request from Veeam support, the software needs to support this solution.
For example splitting a large Teams job into multiple segments for easier trouble shooting and hey, it might actually be the reason for the slowdown.
But that is the worst thing for a service provider, because that means you cant just let the job run and there is no scheduler inside of Veeam to support this use case. You cannot use the normal scheduler for this, because if the jobs overlap it has the cascading effects of ruining all your backups that day.
One client has 35 security group jobs, with Mail/archive, Sites and Ondrive, about 2000 objects per group.
We have been told to split these into Exchange, OneDrive and Sites. 35 jobs split into 3 is 105 jobs which we then have to schedule somewhere and somehow.
If this is such a common request from Veeam support, the software needs to support this solution.
Statistics: Posted by track1044 — Aug 28, 2025 11:00 am
