Veeam Backup for Microsoft 365 • 365 Job design to grow into

Hello. Sorry, I think this has been asked many times. We have a site with about 70 users. At present, they are only using Exchange Online for email and teams. We want to design this site as well as others we do with the best practices in mind. I know Veeam has published several articles on best practices. But for this particular site, I see them migrating a LOT of data from on-prem servers to O365 so we want to build a solid backup strategy now to grow into. We could just do one backup job for the entire organization now but I suspect that will get ugly later as they grow and we want to provide a solid foundation to start. So we were thinking of (4) Backup jobs where the "Backup the following Objects" are all set to "Organization". However, for each backup job, we would edit the Organization and select the "Processing Options" we want to include. For instance, we were thinking of the following:

Backup Job 1: Processing Options Mail and Archive
Backup Job 2: Processing Options OneDrive
Backup Job 3: Processing Options Sites
Backup Job 4: Processing Options Teams

We were thinking that this would also be "dynamic" for each processing option so we do not need to manually "include" new users, new sites, etc. They would just be picked up by the Processing options above. Then as they grow we can get a little more creative if needed to include/exclude specific objects. The backup Repo would be Wasabi with one bucket but individual folders corresponding to the Backup Jobs above (4 separate folders).

Would this work? Any downsides? Am I overthinking it?

Thanks

Statistics: Posted by dhayes16 — Feb 16, 2024 7:54 pm

---