Skip to main content

Hypervisor Fishing - Species Microsoft Hyper-V

  • January 27, 2026
  • 4 comments
  • 35 views

skitch210
Forum|alt.badge.img+1

Hyper-V has been around over 16 years initially released with Server 2008. It can run on most hardware and either on hyperconverged or distributed infrastructure. Since it is based on Windows Server, it can be managed easier with a graphical UI which is familiar with most technical staff. However, that also comes with the stigma that it is Windows šŸ˜€, plus Microsoft had announced the end of Hyper-V as they transition to Azure Local until the Broadcom announcement and then they reversed that decision.

From a use case perspective, it can be used in small distributed (ROBO) deployments or large-scale hosting and Veeam has current customers that reflect this. Microsoft used to have a self-service portal via System Center Service Provider Foundation but that has been discontinued and now there are third party solutions like Hosting Controller or Cloud Assert. It is highly recommended to utilize System Center Virtual Machine Manager (SCVMM) for centralized orchestration and fabric management at the service provider layer.

From a Veeam perspective, Veeam has supported Hyper-V since Nov 2011and has the closest feature parity between VMware and Hyper-V. This includes backup and replication, replication to a Cloud Connect provider, and application awareness of the VMs. One key issue is the lack of VM and storage snapshot integration, so Veeam cannot recover a VM, application items, or files from a storage snapshot of a Hyper-V VM. There is not an IaaS hosting self-service portal for customers to run their own backups or restores. Hyper-V is currently supported by Recovery Orchestrator for backups and automated restores back into Hyper-V and into Azure. Veeam One also has Hyper-V infrastructure monitoring capabilities for hosts, datastores, VMs, VM in-guest processes and services, to include performance charts and alarms.

Ā 

Based on this information, I feel Hyper-V would be a good fit for most use cases, especially for those with limited or no Linux experience. There are cost benefits at the smaller scale based on Windows server licensing. With the Veeam functions added in, you also get more use out of the Advanced and Premium editions with Veeam One and Recovery Orchestrator, and the ability to use Cloud Connect Replication. I would be a little concerned about the future roadmap as Microsoft seems destined to push this to Azure Local, which may be a positive in the long run. Also, good or bad, can get support from Microsoft which is 24/7/365 globally.

4 comments

lukas.k
Forum|alt.badge.img+13
  • Influencer
  • January 28, 2026

Honestly I like Hyper-V and work with that infrastructures for several years now. Many people complain about it being a Microsoft product (obviously) but at the end of the day you get a HV that fits into most of the SMB customers requirements quite perfectly.

Yes, you have a Windows-based platform and yes, many experiences with the Microsoft support might be quite negative (from what I heard through the years) but they have a strong community, a good and detailed knowledgebase / helpcenter - anyways facing some challenges with Broadcom and other competitors this is still a good choice imo.


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • January 28, 2026

I ā€œplayedā€ with HV last Summer/Fall. More specifically, Failover Cluster, as implementing that is ā€œcloseā€ to VMware central virtualization mgmt (vCenter). But, it’s soooo complex! I know VMware is too. But, I’ve been using VMW so long, I think I’ve just slowly migrated with them & their complexity to not pay much notice (and I don’t utilize so many other VMW ā€˜layers’ like vSAN and NSX and monitoring services, ertc).

ā€œBasicā€ HV is ok (no SCVMM and no Clustering), but it’s not really a good scale solution..unless I’m missing something?Ā And I say all that from a SMB perspectiveĀ šŸ˜‰ I wanna like it...and from a very small implementation perspective, it is ok actually. But, not sure it’s something I’d implement in my environment. So far...what I’m liking is XCP-Ng. I haven’t played with Proxmox..but haven’t heard too many good things about them.


lukas.k
Forum|alt.badge.img+13
  • Influencer
  • January 30, 2026

I ā€œplayedā€ with HV last Summer/Fall. More specifically, Failover Cluster, as implementing that is ā€œcloseā€ to VMware central virtualization mgmt (vCenter). But, it’s soooo complex! I know VMware is too. But, I’ve been using VMW so long, I think I’ve just slowly migrated with them & their complexity to not pay much notice (and I don’t utilize so many other VMW ā€˜layers’ like vSAN and NSX and monitoring services, ertc).

ā€œBasicā€ HV is ok (no SCVMM and no Clustering), but it’s not really a good scale solution..unless I’m missing something?Ā And I say all that from a SMB perspectiveĀ šŸ˜‰ I wanna like it...and from a very small implementation perspective, it is ok actually. But, not sure it’s something I’d implement in my environment. So far...what I’m liking is XCP-Ng. I haven’t played with Proxmox..but haven’t heard too many good things about them.

Have nearly zweo experience with XCP-Ng (will absolutely have to come in the future!) but I have a few customers (German banks) that run around 60.000-80.000 VMs all on Hyper-V. And they don’t yet use Azure Local, so I’m looking forward to follow that road with them (from a background perspective 😊).

Ā 

They use scripting a lot so I agree, the vSphere UI is absolutely way easier than Hyper-V!


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • January 30, 2026

​@lukas.kĀ -

Well...I created a few XCP-Ng posts on here last yr to get you started, if you’re interested?Ā šŸ˜‰

Ā