Maintain control of your Microsoft 365 data
Post Reply
matteu
Veeam Legend
Posts: 824
Liked: 128 times
Joined: May 11, 2018 8:42 am
Contact:

Job management

Post by matteu »

Hello,

I have a new installation to perform with a specific use case :

There is 1 VBM365 server all in one but it will be use to backup 8 differents entities from 50 to 500 users

I would like to know if there is a recommendation to use 1 Exchange job for all entities or 1 Exchange job / entity ?
I will use the same logic for Onedrive and Sharepoint and Teams.

The total is lower than the maximal object per job.

I already see : https://bp.veeam.com/vb365/guide/design/jobdesign.html

Thanks for your answer.
Polina
Veeam Software
Posts: 3293
Liked: 794 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: Job management

Post by Polina »

Hi matteu,

A backup job can only contain objects (mailboxes, sites, etc) belonging to the same tenant organization (i.e. in one job you cannot mix objects from different organizations). If you're going to protect 8 different organizations and split backups by protected workload, you will need to create 8 Exchange jobs, 8 OneDrive jobs, and so on.

Makes sense?
matteu
Veeam Legend
Posts: 824
Liked: 128 times
Joined: May 11, 2018 8:42 am
Contact:

Re: Job management

Post by matteu »

They are all on the same organization ^^ but they are not dependent one from the other.
Is there any sense to separate them ?

It's totally ok for me to create :
1 Exchange job :
-Object selected : Organization
-object to process : Mail + Archive
-Object to exclude : Set all what I don't want

Is this a good idea ?
Or better to use a Dynamic Azure AD group base on what criteria ?
Static Azure AD group make non sense for me because I know there will be too much object not added in the group => no backup. (if no catch all job).
Polina
Veeam Software
Posts: 3293
Liked: 794 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: Job management

Post by Polina »

Both options are OK; for small tenants of up to 500 users, the Organization/Mail config should work well. It'll back up all organization mailboxes automatically including new users.

Thanks!
matteu
Veeam Legend
Posts: 824
Liked: 128 times
Joined: May 11, 2018 8:42 am
Contact:

Re: Job management

Post by matteu »

Maybe I didn't give any information.

I have 8 AD forest.
All these forest are sync to Azure inside the same tenant.

So, in my Azure tenant, I have 8 "companies".

The idea is to use 1 VBR server and backup data of the 8 companies.

I could use the design I wrote like 1 exchange job and select organization "mail + archive" or use 8 jobs and use dynamic group based on domain. Each company get his own domain like :
xxx@domain1.com
xxx@domain2.com ....

So I could have AAD group domain1 contains all user with @domain1
AAD group domain2 contains all user with @domain2
And then on VB365 I use AAD group domain1 in job Exchange domain 1
That mean I will have 8 jobs per "company".

You said Job with 500 users is ok to select entire organization but here total user is arround 1500/2000 (don't know exactly now).
Is it better to split it / company maybe ?

Then to be sure to backup all, what do I need ?


Because If I select user group, I will not backup distribution group right ?
If I need to select all existing sharepoint site + futures one, Only select Organization can do it or is there any other solution ?

My issue here is about :
I want to be sure if I create new group, new users, new mail, new teams, new sharepoint site, they are backuped and I don't need to add them manually somewhere.

How do you usually manage it ?
Post Reply

Who is online

Users browsing this forum: bertdhont and 36 guests