V365 job design

A video would be great idea , @damien commenge (once you have the solution) 

@Chris.Childerhose 

To be honest, I read all the documentation, see lot’s of videos about VB365 but nothing to help me to make the design I ask here ^^ .

It’s not about ressource or proxy or repository.

My question is just about if I use job per domain, how to manage them. What would you integrate exactly ? 

Is there a way to say : Domain1 - Exchange job : I want all mail + archive for domain1 and same for sahrepoint, onedrive and teams.

If this is true, how to perform it ? This is my real question :) . There is only demo where people show it for 1 user / 1 group… Ok , it’s good for a POC but here for production, how to manage it better ^^ ? 

This is exactly the help I would like to find here ^^ or if you have some good link about real use case it’s should be perfect too :)

@chri

If it’s for 1 org, how do you manage it exactly ?

I mean, how do you do to be sure “future” object are backup ?

For personnal object it should be easy with dynamic group.

But what about sharepoint site ? or Teams ? 

My english should be really bad because my issue is not about dynamic group xD.

I know what it is and how it works ^^ .

My issue is : when you create sharepoint site, if it’s not personnal site, it will not work with dynamic group or teams right ?

Like my picture attached. Accounting / developpment / … can be added to a dynamic group ?

Same for Teams group ?

Dynamic group contains user or device, not other type normally ^^

I could check all what  I want today. But tomorow, if new sharepoint site is created, that means I need to come here and add it. Isn’t there an other solution ? I know I can do it if I add all organization….

@Chris.Childerhose Thanks for your answer.

I’m thinking about the picture I attach as job design. 

This model seems ok for me and should work fine no ?

Final question is.... Do I need only 4 repositories or do I need 3 / entity + 1 for global sharepoint + 1 for teams.

d:\exchange + d:\onedrive + d:\teams_sharepoint

or

d:\exchange\entity1 + d:\exchange\entity2 + …. + d:\onedrive\entity1 + d:\onedrive\entity2 + …. + d:\teams_sharepoint\entity1 + d:\teams_sharepoint\entity2 + …. + d:\teams\sharepoint\global (common for teams and sharepoint organization backup job)

You could also put the Teams data in the Sharepoint Jobs for each entity since they share most of the same data. You could also exclude your two Entities from the Global Teams job.

@Chris.Childerhose 
Yes, I think this model seems ok for job design.

For repository, I think option 2 is best too because database will be lower and each entiy will have dedicated one. If an issue appears for “X reason” it will be easier to perform new full.

@HangTen416 

I saw in best practice 1 job / service is recommended but Sharepoint and Teams should share the same repository.

I would like an “auto” solution to backup. I would like to avoid to update the job because new Teams group is created… For this, I need to select all the organization to backup teams group.

I think I need 3 repo / entity + 1 common global (share sharepoint not personnal site + all entires teams groups).

If you have a solution to backup Teams without needed to update the job each time a new group is created, I can hear you :)

I guess my question is how big are we talking here.  Sounds pretty sizable.  I would certainly look at specifying with dynamic groups.  I’d probably have one job per domain unless you were going to break things down to one type (Exchange Online/Teams/OneDrive/Sharepoint Online) per job, but the recommendation of splitting that out should be going away with new versions (I don’t think the latest version made that recommendations obsolete yet).  For me, really, it comes down to what makes the most sense from a data management perspective.  Splitting it up too much makes it harder to manage and perhaps harder to run restores, but obviously one lump repository and job seems like it may not be sufficient for a larger org or orgs as well.  For my individual smaller clients, I have on repo and one backup job per Organization.  It works, though for my internal organization, it is pretty sizable and may benefit from breaking things up a little in backup run time and perhaps breaking up the sources.  I’ll note that I am backing up the entire organization, but for some of my clients, I’m using an AD group that is synced to Entra ID that specifies the license assignment, so I also specify that group as the source of objects to be backed up.  However, I still have to specify additional objects to backup such as resources and shared mailboxes, etc.  I’d like Veeam to develop that functionality a bit more so that you can dynamically select those types of accounts/mailboxes, but unless it was released in the latest version, that functionality doesn’t yet exist.