Also what should be the sizing off the VBR server itself, what are the recommendations for this?
On top of the Backup Jobs we will have Backup Copy Jobs also.
 

Hey @NemanjaJanicic ... @MicoolPaul kinda shared about your job  usage questions in a post a few mos back with regards to all VMs in 1 job vs segregated. He was testing VBR performance of pending tasks. My recommendation is for large file servers of around 3-4TB & larger, put those in their own job so as not to delay getting smaller VMs backed up. Then group all your smaller VMs in a job. When using per-VM Repo setting, you can have about 300 VMs in a job as noted in the Veeam BP Guide.

You can look there for VBR sizing as well. BTW, are you using an all-in-one VBR setup to where your Veeam server is also your Proxy & Repo? If so, look in the BP Guide on sizing for those other 2 roles as well. Whatever compute you give your VBR server, you'll have to add compute for the Proxy & Repo roles as well.

Hope that helps. 

Hey @coolsport00 ,

Repo’s will be connected via iSCSI to VMs specifically for that then connected to VBR as repositories.

We don’t have any off-host proxies.
Plan is to have off-host proxy for our largest VM.

For Proxies I think that our VBR is proxy by default and on-host proxies should be.
 

@NemanjaJanicic yep, that sounds like a very viable implementation design plan to go with. Just reference the User Guide for Sys Req’s , and the BP Guide for Sizing and you should be golden

It’s recommended to group the same os vms in one backup job for better deduplication ratio.

Hello i don’t understand your answer, this is only the case if @NemanjaJanicic is using single file backup.

Backup Chain Formats - User Guide for Microsoft Hyper-V (veeam.com)

The organisation of backup jobs can sometimes be adapted to several factors:
- Internal organisation 
- Workload (AAIP, indexing, huge servers...)

@coolsport00 I like what Shane suggested . BTW from my understanding is the 300 limits was before V12. I played with this limit in the past 

You can add all your 3 hypervisors in a single jobs and exclude specifics servers and process them to a dedicated jobs. All new workload created on these hypervisors will be backuped, it could give you some flexibility.

Hi @BertrandFR - the 300 is in the BP Guide here , but yes...this was way before v12. We talked about VMs per job in the VMCA v1 Course back in I believe 2019...and this number was thown out there way back then too

Hi @NemanjaJanicic - did we answer your question for you? Let us know if not.

Thanks!