That’s wasteful. And expensive.

The fix is virtualization — running multiple “virtual machines” on one physical server. Instead of buying three servers for three jobs, you buy one decent box and run three virtual servers on it. Less hardware, less power, less cooling, less stuff to break.

But when you start looking into it, you hit a wall: VMware or Hyper-V? Everyone has an opinion. Most of the internet swears by VMware (or they did before Broadcom bought VMware, now everyone is looking to jump ship). Hyper-V doesn’t get as much attention, but it’s widely used and perfectly capable. And nobody explains it in a way that actually helps a small business owner decide.

So let’s fix that.

What Is Virtualization, Quick Version?

A virtual machine (VM) is a computer that runs inside another computer. It thinks it’s real — it’s got its own operating system, its own memory, its own network connection — but it’s actually sharing the physical hardware with other VMs.

The software that makes this happen is called a hypervisor. VMware and Hyper-V are both hypervisors. They’re the layer between your physical hardware and the virtual machines running on top.

Why bother? Three reasons:

1. Consolidation. One physical server doing the work of three or four.
2. Isolation. If one VM crashes, the others keep running. Your file server doesn’t take down your accounting app.
3. Recovery. You can back up an entire VM — operating system, apps, data, all of it — as a single unit. When something goes wrong, you restore the whole thing in minutes instead of reinstalling from scratch.

VMware vSphere (ESXi)

VMware is the big name in virtualization. They’ve been doing it the longest, and their product — vSphere ESXi — is what most enterprises run.

The good:

• Mature and rock-solid. This thing has been battle-tested in data centres for nearly two decades. It just works.
• Excellent performance. VMware’s hypervisor is lean and efficient. You get more out of your hardware.
• vSphere Client. The web interface is clean and intuitive. Managing VMs, checking performance, setting up networks — it all makes sense.
• Snapshots. Take a point-in-time snapshot of a VM before you make changes. If it goes sideways, roll back. Invaluable.
• Huge ecosystem. Every backup tool, monitoring system, and management platform supports VMware. It’s the default.

The not-so-good:

• It’s expensive. VMware vSphere licensing isn’t cheap, and since Broadcom acquired VMware, pricing has gotten worse. The free version (ESXi Free) exists but is severely limited — no vMotion, no central management, no backup API access. You basically can’t use it properly in production.
• Broadcom uncertainty. Since the Broadcom acquisition, VMware has been killing off free tiers, raising prices, and generally making people nervous. A lot of businesses are actively looking for alternatives right now.
• Overkill for small setups. If you’re running two or three VMs, you probably don’t need enterprise-grade virtualization.

Microsoft Hyper-V

Hyper-V is Microsoft’s hypervisor. It’s built into Windows Server and Windows 10/11 Pro/Enterprise etc… Windows 10/11 Home edition doesn’t include Hyper-V.

The good:

• It’s included with Windows Server. If you’re already running Windows Server (and most small businesses are), Hyper-V comes with it. No extra licensing cost.
• Windows integration. If your business runs Windows — and it does — Hyper-V fits right in. Same management tools, same Active Directory, same update cycle.
• Hyper-V Manager is decent. It’s not as polished as VMware’s interface, but it works. For a small number of VMs, it’s perfectly fine.
• No vendor lock-in anxiety. Microsoft isn’t going to buy themselves and triple the price. Hyper-V isn’t going anywhere.

The not-so-good:

• Linux VM support is ok, but VMware and Proxmox still tend to offer a smoother experience.
• The interface feels dated. Hyper-V Manager looks like it was designed in 2010 and never updated. It works, but it’s not pretty.
• Snapshots are called “checkpoints.” They work fine, but they’re easy to misuse — especially if you leave them in place for too long. Like VMware snapshots, they’re not backups
• Less third-party support. Some backup tools and management platforms support Hyper-V, but the ecosystem isn’t as deep as VMware’s.

What About Open Source? Proxmox and XCP-ng

I’d be doing you a disservice if I didn’t mention the open-source options. If you’re reading this blog, there’s a decent chance you’re the kind of person who’d rather run free software than pay for a licence — I know I am.

Proxmox VE is the one to watch. It’s a full virtualisation platform built on Debian Linux, with a proper web interface, built-in firewall, software-defined storage, and support for both VMs and containers. The base platform is completely free and open source (AGPLv3). They offer a paid subscription for enterprise support and access to a more stable package repository, but the free community repo works fine. Proxmox has been around since 2008 and it’s mature, well-documented, and genuinely good.

The kicker: Proxmox includes backup built in. No separate Veeam licence, no API restrictions. You get scheduled backups, replication, and even built-in clustering — features that cost thousands on VMware. For a small business running a handful of VMs, it’s hard to argue against.

XCP-ng is an open-source fork of Citrix Hypervisor (formerly XenServer), typically paired with Xen Orchestra for management, which is open source with optional paid support. XCP-ng is solid and performant — Xen has powered large-scale cloud infrastructure (AWS relied on it for many years). With XCP-ng, management is typically done via the Xen Orchestra web UI, which is feature-rich, though generally considered less polished and tightly integrated than Proxmox’s interface.

The honest comparison: Proxmox is the better choice for most small businesses. The web interface is excellent, the community is active, the documentation is good, and the backup story is simpler. XCP-ng is technically solid but can take a bit more effort to set up and manage, especially compared to Proxmox’s all-in-one experience.

The catch with open source: You’re your own support. There’s no 1-800 number. If something breaks at 2am, you’re on the forums and the documentation. If you’ve got Linux chops (or want to learn), that’s fine. If you need hand-holding, Hyper-V with its Windows familiarity might be the safer bet.

I’ll cover Proxmox installation in detail on Patreon, with full setup, VM creation, and backup configuration walkthroughs. This one’s worth getting right.

Head to Head

My Honest Take for Small Business

If you’re a small business running a handful of Windows-based VMs — file server, maybe a line-of-business app, maybe a domain controller — Hyper-V is the pragmatic choice.

It’s free (or already included), it’s from a vendor you’re already paying, and it does the job well enough. You’re not running a data centre. You don’t need vMotion and distributed switches and all the enterprise bells and whistles. You need something that runs your VMs reliably and doesn’t cost extra.

But — if you’re comfortable with Linux, or willing to learn, Proxmox is the one I’d actually recommend. It’s free, it’s open source, the web interface is excellent, and the built-in backup alone saves you from needing Veeam. For a FOSS-minded small business, it’s the sweet spot between capability and complexity. XCP-ng is solid too, but Proxmox has the edge in usability and community.

Save the VMware budget for when you’ve got ten VMs, a mix of Windows and Linux, and someone managing it full time. That’s when it earns its keep.

The Real Question Isn’t VMware vs Hyper-V

It’s whether you should be virtualising at all.

If you’ve got a single physical server doing one thing, you’re wasting money. Hardware is cheap compared to the downtime when that one server dies and you’re reinstalling everything from scratch.

Virtualise it. Pick Hyper-V if you want the familiar Windows path, or Proxmox if you’re ready to go open source. Get your VMs running. Set up proper backups — and I mean proper, not “copy the VHD file while it’s running.” Use something that’s VM-aware.

That’s where the real payoff is. Not in which hypervisor you pick, but in actually doing it.

I’ve put together a complete installation and backup guide on Patreon — covering both VMware ESXi and Proxmox VE, with step-by-step VM creation and backup configuration for each. Grab the guide here.