Check this link for some best practices - https://bp.veeam.com/vb365/guide/design/jobdesign.html
Dynamic groups work well.
From 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?
From 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.
Hi,
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.