Proxmox in business: planning operation, backup and migration

Proxmox VE can be a good virtualisation platform for businesses. Besides cost, the decision depends on your applications, the skills of whoever runs it and how quickly you need to recover. I describe my experience with environments of one to three hosts from 2024 and 2025 and the questions I settle before a migration.

Why I usually suggest Proxmox

Proxmox VE is an open-source virtualisation platform based on Debian. It manages virtual machines and containers through a web interface and comes with clustering, high availability and its own backup solution. For the environments I look after, typically one to three hosts running a domain controller, file services, line-of-business applications and a handful of other servers, it has the features required.

Three things decide it for me. The platform is economical for small environments, also since VMware changed its licensing model. It is openly documented, so another provider or your in-house IT can carry on working with it. And virtualisation and backup come from the same source and fit together.

Moving from VMware or Hyper-V

I have done both with clients. Since version 8.2, Proxmox VE includes an import wizard that takes virtual machines directly from an ESXi host and carries over most of their configuration. For Hyper-V, I convert the machines’ disk files and import them. In both cases the transfer itself is rarely the hard part.

The effort lies in the preparation. Windows systems need the VirtIO drivers so that disks and network run at full speed. Licences tied to hardware characteristics may need reactivating. And for every machine I clarify beforehand how long it may be down and in which order the services have to come back up.

A single host or a cluster?

Host or cluster: the decision

How long may an outage last?

A restore from backup is fast enough

Single hostwith good backups

That takes too long

Clusterof several hosts

A single host with good backups is enough for many small companies: if it fails, I restore the machines from backup. In a cluster I can move virtual machines while they are running, for example during maintenance. If hardware fails, the cluster restarts them on another host.

For a cluster with automatic high availability, Proxmox requires at least three votes, so that the majority vote (quorum) still works when one host is down. If a cluster loses its majority, no further changes can be made. With two hosts, a QDevice provides the third vote: a small device outside the cluster. Proxmox supports this for clusters with an even number of nodes and advises against it for an odd number. The machines also need shared or replicated storage so that another host can take them over.

Backup in two stages

How the two backup stages run

Stage 1 runs locally at night, stage 2 transfers every backup over the following day.

1. Proxmox hostvirtual machines
2. Proxmox Backup Serverlocal, nightly, changed data blocks only
3. own copy

   External storageor a second backup server

   managed copy

   Data centrein Germany, pulls the data itself, read-only

For backups I use Proxmox Backup Server. I deliberately keep the first stage of the backup close to the server host. Local backups finish quickly and place little load on the server. As only changed data blocks are stored, storage use stays manageable.

A local backup on its own does not protect against hardware failure, fire or an attack that reaches the host. Hence the second stage. It can run during business hours as well. I limit the bandwidth for each sync job, so nobody in the office notices.

For the off-site copy I offer a managed backup on my own servers in German data centres. This copy sits in a different network from the client’s systems, and I limit permissions in both directions. The backup system in the data centre pulls the data itself and has read-only access to the client network. In turn, the client system has no write access to the backup system. So an attacker who takes over one side cannot use this connection to change or delete data on the other. That is not physical separation like an offline disk kept elsewhere; where the level of protection required calls for it, an additional, separately stored copy belongs in the plan.

Does Windows Server run on Proxmox?

This question comes up almost every time. The short answer: Windows Server runs on Proxmox, and at my clients it runs that way without problems day to day.

• Licensing: Windows Server Standard and Datacenter are usually licensed by the physical cores of the host, on Proxmox too. You need at least 8 core licences per processor and 16 per server. Standard edition allows two virtual Windows servers on a fully licensed host, Datacenter an unlimited number. Since Windows Server 2025 you can instead license per virtual machine, with at least 8 core licences per VM; this requires Software Assurance or subscription licences. If you move machines between hosts in a cluster, clarify beforehand which hosts need to be licensed for that.
• Support: Proxmox is not one of the platforms with which Microsoft has a joint support agreement. Microsoft does not officially test its software there. For customers with Premier support, Microsoft will still investigate, but may require a fault to be reproduced under Hyper-V or on physical hardware first. For small environments without such a contract this rarely matters, but I point it out in advance.
• Technology: VirtIO drivers, the QEMU guest agent and suitable processor and disk settings are part of the basic setup. Proxmox documents its own recommendations for Windows guests.

When is switching not worth it?

It is rare, but it happens. If a company has an in-house IT team that works with VMware or Hyper-V every day and has the environment firmly under control, that knowledge often outweighs the benefits of switching. A platform your own team does not know is the worse choice when something goes wrong. In those cases I recommend staying put and look after backup, updates and documentation instead.

Frequently asked questions

Is Proxmox suitable for businesses?

For many small and medium-sized companies, yes, and for new virtualisation I usually suggest it. Proxmox VE handles typical environments of one to three hosts with a domain controller, file services and line-of-business applications, and it remains economical since VMware changed its licensing model. Your applications and the skills of the people running the environment matter just as much.

How much work is a move from VMware to Proxmox?

Transferring the virtual machines is rarely the hard part: since version 8.2, an import wizard takes them directly from an ESXi host. The effort lies in the preparation, such as VirtIO drivers for Windows, licences that may need reactivating, and how long each machine may be down.

What should backup look like on Proxmox?

I back up in two stages with Proxmox Backup Server. The nightly backup runs locally and finishes quickly; over the following day, every backup is then copied with limited bandwidth to external storage or a second backup server, because a local backup on its own does not protect against hardware failure, fire or an attack.

Sources

• Import wizard for VMware ESXi: Proxmox – Proxmox Virtual Environment 8.2 with Import Wizard released
• Moving from VMware and Hyper-V: Proxmox VE Wiki – Migrate to Proxmox VE
• Cluster and quorum: Proxmox VE documentation – Cluster Manager
• Sync and bandwidth limits: Proxmox Backup Server – Managing Remotes & Sync
• Windows guests: Proxmox VE Wiki – Windows 2022 guest best practices
• Windows Server licensing: Microsoft – Windows Server 2025 Licensing Guidance
• Support on other virtualisation platforms: Microsoft Learn – Support policy for Microsoft software that runs on non-Microsoft hardware virtualization software