+1Hello,
I have 900 M365 users and now i communicate with our veeam partner to purchase VDC license.
The vendor say we must make groups of our 900 users. Here i want to know it’s mandatory we should make some group for my 900 users? If yes, is there any best practice what kind of groups (should i make group by internal department or by any object will be backup)?
+21Check this link for some best practices - https://bp.veeam.com/vb365/guide/design/jobdesign.html
Dynamic groups work well.
+1From what i read, it’s recommended to make group by object what will be backup.
Example group for backup teams, group for backup exchange, group for backup sharepoint.
Any other pov?
+21From what i read, it’s recommended to make group by object what will be backup.
Example group for backup teams, group for backup exchange, group for backup sharepoint.
Any other pov?
This is usually the best route to make backups perform well.
+23Hi,
There can be multiple reasons behind this.
Firstly, there are two license models, fixed & variable. With fixed you can’t go over the license purchase amount whilst with variable you can but will incur overages if you do. If you’re not backing up your entire organisation you’d need at least one group to enumerate who needs protecting.
Other reasons will be for allocation of users to requirements such as if you have multiple geolocations you want your backups stored within, or if you want multiple retention periods, or even different backup frequencies.
It might also be because your organisation has the potential to scale beyond reasonable sizing for a singular backup job, so proactively creating your jobs in a way to support this can make sense.
If in doubt reach out to your Veeam Partner for guidance on shaping this.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
