Proxmox Virtualization & HA Clusters

Proxmox VE installation for single nodes and multi-node HA clusters, with Ceph storage, optimized VM/LXC templates, and live migration.

Proxmox VE is a solid foundation for self-hosted virtualization, but the difference between 'it boots' and 'it survives a node failure at 3 AM' is in the details — quorum, fencing, shared storage, and network design. I set up Proxmox environments ranging from a single all-in-one node to multi-node HA clusters with Ceph.

For single-node setups, that means a clean install, sensible storage layout (ZFS or LVM-thin), and optimized VM/LXC templates so spinning up a new container or VM takes minutes, not hours.

For clusters, it means Corosync configuration tuned for your network, Ceph distributed storage spread across nodes for shared, replicated block storage, and tested failover — so if a node goes down, the VMs that were on it come back up on another node automatically.

What's Included

Single-node Proxmox VE installation, storage layout, and hardening
Multi-node HA cluster setup with Corosync quorum and fencing
Ceph distributed storage configuration across cluster nodes
Optimized VM and LXC templates for fast provisioning
Network configuration — bridges, VLANs, and bonded interfaces
Proxmox Backup Server setup and tested live migration / failover

Technologies & Tools

Proxmox VECephZFSLXCKVM/QEMUProxmox Backup ServerCorosync

Frequently Asked Questions

How many nodes do I need for a real HA cluster?

Three is the practical minimum — Proxmox's quorum mechanism needs an odd number of voting members, and three nodes lets the cluster survive losing one without losing quorum.

Do I need Ceph, or is shared storage overkill for my setup?

Ceph makes sense once you want a VM to migrate to another node and keep running without copying its disk first. For a single node or a cluster where brief downtime during migration is fine, ZFS with replication is often simpler and still solid.

Can you migrate existing VMs from VMware, Hyper-V, or a single Proxmox node into a new cluster?

Yes — VM disk images can be converted and imported, and the migration can usually be staged to keep downtime to a single short maintenance window per VM.

Will setting this up cause downtime on my current server?

For a fresh install, no — it's a separate environment until you're ready to move workloads over. For converting an existing single server into a cluster node, we plan around a maintenance window.

Need Help With This?

Tell me about your setup and what you're trying to do. I'll get back to you with next steps.

Get in Touch

What's Included

Single-node Proxmox VE installation, storage layout, and hardening

Multi-node HA cluster setup with Corosync quorum and fencing

Ceph distributed storage configuration across cluster nodes

Optimized VM and LXC templates for fast provisioning

Network configuration — bridges, VLANs, and bonded interfaces

Proxmox Backup Server setup and tested live migration / failover