Hi all,
interested to hear what backup job designs seem to be the way forward these days...? Fewer big jobs with dozens of VMs? Or SLA focussed jobs with dozens of VMs? Or lots of little jobs with service focussed small amounts of VMs? Or separate jobs for SQL and Sharepoint? etc. ?
-
- Expert
- Posts: 206
- Liked: 14 times
- Joined: Jul 23, 2013 9:14 am
- Full Name: Dazza
- Contact:
-
- Veeam Legend
- Posts: 418
- Liked: 243 times
- Joined: Apr 11, 2023 1:18 pm
- Full Name: Tyler Jurgens
- Contact:
Re: VBR Backup Job Design
I prefer individual jobs per VMs. Only because you can get really granular with a single VM job, rather than larger jobs. If that's too daunting (too many VMs), then I go for grouping like VMs into like Jobs. Eg: AD servers may all have the same retention policy, AAP settings, etc, so group them together.
Its mostly a case of 'what do you want to manage?' rather than what the community in general uses. I've seen countless company's Veeam setups and I am telling you - no two setups are the same. Veeam is so powerful and so configurable, you can accomplish the same task multiple different ways.
Have an end goal in mind and configure toward that.
Its mostly a case of 'what do you want to manage?' rather than what the community in general uses. I've seen countless company's Veeam setups and I am telling you - no two setups are the same. Veeam is so powerful and so configurable, you can accomplish the same task multiple different ways.
Have an end goal in mind and configure toward that.
Tyler Jurgens
Veeam Legend x3 | vExpert ** | VMCE | VCP 2020 | Tanzu Vanguard | VUG Canada Leader | VMUG Calgary Leader
Blog: https://explosive.cloud
Twitter: @Tyler_Jurgens BlueSky: @explosive.cloud
Veeam Legend x3 | vExpert ** | VMCE | VCP 2020 | Tanzu Vanguard | VUG Canada Leader | VMUG Calgary Leader
Blog: https://explosive.cloud
Twitter: @Tyler_Jurgens BlueSky: @explosive.cloud
-
- Expert
- Posts: 206
- Liked: 14 times
- Joined: Jul 23, 2013 9:14 am
- Full Name: Dazza
- Contact:
Re: VBR Backup Job Design
Per VM would be too painful. Probably I'd likely setup as follows:
Prod - AD
Prod - SQL
Prod - Sharepoint
Prod - General
Non-Prod - SQL
Non-Prod - Sharepoint
Non-Prod - General
Something like this.
As you say, it's the outcome that drives the design to some degree.
Prod - AD
Prod - SQL
Prod - Sharepoint
Prod - General
Non-Prod - SQL
Non-Prod - Sharepoint
Non-Prod - General
Something like this.
As you say, it's the outcome that drives the design to some degree.
-
- Veeam Legend
- Posts: 212
- Liked: 60 times
- Joined: Mar 22, 2017 11:10 am
- Full Name: Mark Boothman
- Location: Darlington, United Kingdom
- Contact:
Re: VBR Backup Job Design
For our clients i tend to go with creating jobs based on logical grouping like above.
It has the advantage then that usually if a new member of the team joins restore requests should be quite easily identified based on job grouping.
This approach also aids when looking at a recovery plan in the event having having to recover from something catastrophic.
It has the advantage then that usually if a new member of the team joins restore requests should be quite easily identified based on job grouping.
This approach also aids when looking at a recovery plan in the event having having to recover from something catastrophic.
Who is online
Users browsing this forum: Baidu [Spider], Semrush [Bot] and 49 guests