Help me understand

[Zew]

Hello all you legends,

Let me start by saying I appreciate all the hard work done by the Veeam staff for making VBR an amazing product. VBM365... Meh.

The background, we had VBR running, life was great, M365 happened, the cloud was forced down our throats. The industry had to adapt, and thus VBM365 was born.

Now the crux of my problem maybe a fault of my own, but I'm looking for help in coming up with a constructive solution to my problem.

I created the jobs for M365, one job for every user that exists (this doesn't scale well, so probably not the best approach), also the root of my problem. When a user leaves, and I delete their account, the job simple falls to a warning (nothing to process). However, again in VBR, if I delete a job the data simply moves to the orphaned node, life's good and easy. However I can't seem to do that in VBM365 as there is no orphaned node. All restoring appear to happen at the backup job itself, again different from VBR.

veeam-backup-for-microsoft-365-f47/remo ... 68517.html

as noted here, the answer is to "do nothing". I could just leave the job as is, or as I have now disabled it. I don't feel this is the best approach for backing up M365 data. Also for copying the data, I rely on VBR to copy the files using a file backup job after disabling the Veeam M365 services, then starting the services back up when the job completes.

I would like help in understanding what the best practice approach is with this type of a design? Thanks everyone

[karsten123]

veeambp.com

[DaStivi]

There are multiple approaches — but creating one job per user is probably the worst one.

How many users are we talking about here?

Normally, as long as I'm dealing with just a few hundred users, I stick to a single job — maybe two:

one for Users
one for Teams/SharePoint

In larger environments, like with 15,000 users, I use dynamic groups (as recommended on veeambp.com).
for example, 16 User jobs, each handling roughly 1,000 users.

User jobs are usually easy to manage.
Teams/SharePoint, on the other hand, is a whole different story…


regarding the "Repo" ... yes as you've noticed, each jobs create a "restore-point" in a repo thats bound to your M365-Tenant (organization)
you can't just see this as orphaned or something similiar like in VBR.... theoretically there are powershell commands to delete these (User-) Objects from the backup repostory! if you don't delete them they where just in the retention period you set on the repository.

[Zew]

Thanks DaStivi,

Really appreciate some context and examples from the resource posted. I don't think I'll ever like cloud. However, I am thankful for the community and Veeam for making the worst stuff (*cough* Broadcom) easier to bare by providing support for other platforms and frameworks.

I guess then the whole idea is there's just gong to 1 job in the entire VBM365 product? How do others do backup copies of this stuff? Right now, I have to disable the M365 services and run file copy jobs on VBR itself.

I'll find some time to check out veeambp.com thanks for the help reference.