Hi ​@Edy,

Installing VBR on a VM should be the current best practice. A VM is more portable (you can upgrade the virtual hardware, extend disks and work with snapshots prior upgrading) than physical hardware so I recommend installing VBR on a VM and working with physical proxies (in case of FC) and repo if required.

The goal of a VM imo is to avoid re-installing the Veeam software in case of a failure which takes too much time. In case you run a physical server you need to re-install the software elsewhere which can be avoided if you are using a VM.

For ROBO scenarios (remote site offices etc.) it might make sense to use a simple all-in-one installation with a physical node running all the Veeam services including VBR but I don’t reommend this for main sites.

Hope that helps! Best regards

Lukas

Hi ​@Edy,

you can sure do that and benefit from features like HA and so on. For me it always depends on the Customer I´m facing and the budged given.

If you want to install everything physical you would need at least two physical servers because i usually install the hardened repository which runs on Linux, therefor you would need a second windows system with separate licensing for veeam.

running it virtual you can leverage all the advantages that come with the environment such as high availability, scalability, etc. On the other hand you are dependent on your Infrastructure running for using VBR. 

So i think its hard to say if the one or the other approach is the way to go. 

Regards

Chalid

Hey, I’m in phase with ​@lukas.k 
You could also find really good information in this old topic : 
 

Wow  - thank you for the answers. Very helpful and yes I think, the VM route makes sense for this client. It will be a node Proxmox environment and we have a physical server for the repository, big enough and we also plan to a copy job for offsite storage to another location. 

I will need to study the other thread mentioned.

Cheers, 

Edy

This will be a good solution and be sure to check out the Proxmox information here - https://helpcenter.veeam.com/docs/vbproxmoxve/userguide/configuration.html?ver=1

i have as well physical repositories in onpremise environments of customer, but VBR as VM only.

Bring up VM is very easy instead of physical server. By patching etc, you can create snapshot.

You can have more HA of it like stretched datastore, replication of it, backup by another VBR.

Even you will loose VBR, you can build new VM, install Veeam and configure it, then you can scan repository and you will have back backups.

Thank you Marcel for the input. Appreciate it!

Lots of great assistance from everyone in the community! I also agree that VBR on a VM should be best practice.

When you’re ready, be sure to select the “Best Answer” so this Question is completed, and so that others may find it more quickly in the future.