[Feture Request] - HyperV Role on Veeam Backup and replication physical server

[some_user]

Hello

Is there a plan to extend HyperV host support to include Hyper-V role running on the same server as Veeam Backup & Replication ?
I udenstand that, for security and functional reasons, not everything is enabled on a single piece of hardware by default.
However, I would like to be able to use resources of the backup server (Storage, RAM, CPU) to create Virtual Lab and automate backup consistency and VM recovery testing.

Additionaly, deploy Veem ONE as a virtual machine on the same host as the backup server also seems like a good solution.
At the moment, however, we are unable to protect such a VM with backup, beceause the current version 12.x does not support adding a Hyper-V host when it is running on the same physical machine as Veeam Backup & Replication.

[david.domask]

Hello, welcome to the forums.

Currently no plans to change this -- Microsoft has been consistently clear not to install software to the parent partition of a Hyper-V host. From experience, it will cause a lot of issues with both the backup / restore operations and Hyper-V operations.

Similarly, I'm not sure I understand your goal here:

> However, I would like to be able to use resources of the backup server (Storage, RAM, CPU) to create Virtual Lab and automate backup consistency and VM recovery testing.

The virtual lab is deployed on the host itself, and the lab doesn't really need a ton of resources. I'm not quite getting why it would need to be deployed on the parent partition itself.

All in all, the backup server should be a VM on the host or hosted on another server (ideal scenario), not on the parent partition of the Hyper-V host itself.

[some_user]

I am not sure if we interpret the term primary partition in the same way.

I am considering a scenario in which the physical server running Veeam Backup and Replication on dedicated physcial server with dedicated an parted storage:

1. NVME - divided into separate partition:
a) one for the operating system and related components (MS WINDows server, bootable partition, and so on)
b) separate partition dedicated for HyperV VM
2. RAID 50 with a large capacity on spinning disk, used as a local backup repository.

The backup server will protects both ESXi and Hyper-V hosts by performing backups of the virtual machines running on those hosts.

On the MS Windows Server (physical host), where Veeam Backup and Replication togeted with the management console is installed, the HyperV role is also enabled. Within Hyper-V, there is a virtual machine running the Veeam ONE backup reporting application.

I would like to use the Hyper-V role installed on the backup server and take advantage of its available spare resources (RAM, CPU, and disk), without consuming resources from production ESXi and Hyper-V servers.

The disk layout is separated — including physical disks, logical volumes, and partitions. Them this is not the same partiotio as You wrote ealier in my meaning.

[some_user]

Is there any plans to or maybe Veeam 13 has it already included to get possibility to backup vms hosted on hyperv running on the same hardware as B&R Server ?
I have already B&R as physical server and one VM on the same server for VEEAM ONE Reporting tool, and i need to backup this Veeam ONE VM. It will be nice to backup this vm with the same as rest workloads = B&R

[david.domask]

b) separate partition dedicated for HyperV VM

This part is fine, the main point is as I wrote that you should not install software to the parent partition. I'm not quite understanding your schema here fully, but as I get it the partition that you want to put Veeam products on will be a managed VM, not running directly on the parent partition of Hyper-V -- as long as it's a VM being managed by the Hyper-V resources, that part is fine, the physical location isn't as relevant, it's about resource management.

But I'm not sure I fully get your schema as noted, and if the resources on the partition Veeam uses are not managed and "compete" for resources with the hypervisor itself, that would not be supported and will likely cause issues with operations.