There will be no more physical machines in this project, and therefore any scenario/architecture for Veeam Backup and Replication which demands additional physical machines is not to be considered for this project (for each physical machine has to be audited and certified previously to being put into production, and that auditing and certification process is extremely expensive on a per-physical machine count). The physical machines budgeted for this project are three: two Big Workstations which will directly manage a plethora of medical equipment, and one physical Server with Hyper-V where several VMs will live (database server, calculus server, etc.). There is a way to offload the host by deploying off-host backup proxy to separate physical machine with Hyper-V role enabled. You can install backup server in the VM, however, the most part of the components for the processing will be deployed directly to the source host ( on-host backup). PS: I am a long time Backup Exec user, but I'm new to Veeam, and by perusing the Veeam literature it seems VBR uses a 'infraestructure' different from BE.ĭGrinev wrote:Hi and welcome to the community! If I install VBR in its own VM, would I need to connect that VM to VLAN-1 and VLAN-2 in order to 'reach' the VMs to be backed up? I would prefer to install VBR in its own VM, so that the Hyper-V host stays as pristine as possible will that option make it harder to set up and manage VBR? Should I access the Synology NAS vía SMB, or vía iSCSI? My question is: where would it be best to install VBR - in its own VM, or directly on the Hyper-V host? The backups will be done with Veeam Backup & Recovery 9.5. There will also be VLAN-3 for the backup's network traffic to a Synology NAS, and VLAN-4 just to manage the Hyper-V host.

VMs 1, 2 and 3 will exist in VLAN-1 separted from VMs 4, 5 and 6, which will exist in VLAN-2.

For a new project in a client we are setting up a single Hyper-V host where it is expected 6 virtual machines will live.

Veeam hyper v backup best practices