I have no case number because my topic isn't an issue but more asking for some thoughts I may have missed. We use VBO version 7.1.0.2031. When we started with VBO we created one job per workload pointing to separate repositories and I was aware, that we have to change that to a more granular handling when migrating more users and data to M365 in favor for data storage and processing load balancing. I’m aware of the best practices and techniques for load balancing. Because dynamic groups for load balancing was no option for me and load balancing for SharePoint/Teams is only available through custom scripting respectively using one of the scripts in custom Github repos or Veeam script repo (vb365-JobManager for instance). I created my own PowerShell VBO-JobManager handling SharePoint/Teams and user workloads (Exchange/ExchangeArchive/Onedrive) that dynamically adds and removes the corresponding workload objects based on the idea to split objects into 4 groups using the first character of the siteid (SharePoint) or officeid (all other workloads). That is working really well, except one thing: Currently it treats SharePoint and Teams completely independent. This works technically but ignores the best practices (to point the connected team for a site to the same repository). A site with a siteid starting with “0” would be added to a different job than the connected team with an officeid starting with “f”. Now to my question: Currently it is not possible to do a strong mapping by e.g. group object id, that have both the site and team have in common. Is there a better way to match site and corresponding team and put them in the same job than…
- Match site and team the same way VB365-JobManager does (get alias of team group email address and compare it with site name or using displayname of team and name of site).
- Even though I get only around 40, where the corresponding site cannot be matched. It isn’t sustainable/reliable enough for me.
- Using parameter “-NotInJob”, report not matching teams and add them manually. Could be difficult when also removing not matching teams (due to deletion). I cannot separate keeping not matching but wanted teams and indeed not existing teams.
- Make sure fields for comparison/connecting site and team are identical using a process with the help of additional scripts (e.g. “-NotInJob” parameter).
- Using the “-NotInJob” Parameter to add all not matchable teams in a separate job and ignore best practices
- Using the catch all job mentioned in the best practices
- We don’t want that because of the downsides also mentioned in bp.
- Leveraging additional scripts and app registration in M365.
- No option because we don’t want to establish a parallel connection. My script is running without an addition service user exclusively leveraging Veeam capabilities.
I appreciate any discussion input or ideas. Thanks.
Daniel