Proxmox VE Clustering and Ceph Guides
Proxmox Lab focuses on the decisions behind a Proxmox VE cluster: voting majority, independent network paths, accessible guest storage, and enough capacity to recover after a node fails. Start with Proxmox VE cluster planning to work through two-node QDevice arrangements, Corosync link redundancy, shared storage, and the limits of local replication. Use that guide to write down the failure your design must survive before choosing hardware.
The Ceph scope centers on operations: replica placement, OSD memory, storage-network separation, and capacity during recovery. The planning guide introduces those decisions alongside quorum and HA. Each article cites the documentation behind its technical guidance so you can compare the assumptions with your own configuration.
For an existing outage, follow the Proxmox no-quorum troubleshooting guide. For an incoming VMware estate, use the VMware vSphere to Proxmox VE migration guide to plan import eligibility, guest configuration, and cutover checks. The articles below are listed newest first; choose the entry that matches your current planning or recovery task.
-
Proxmox LXC vs VM Explained: Which to Use and When
Proxmox LXC vs VM explained: containers share the host kernel and cost little to run; VMs add isolation, live migration and any OS. When to use each.
-
VMware vSphere to Proxmox VE Migration: Licensing & Paths
Plan a VMware vSphere to Proxmox VE migration: licensing scope, ESXi import limits, OVF move paths, guest drivers, cutover checks, and rollback.
-
Proxmox No Quorum (500): Diagnose and Fix Corosync
Diagnose Proxmox cluster not ready/no quorum (500) errors with pvecm status, Corosync checks, QDevice guidance, and safe single-node recovery steps.
-
Proxmox VE Cluster Planning: Quorum, Storage, Network
Plan a Proxmox VE cluster with two-node QDevice voting, redundant Corosync links, shared storage, Ceph capacity, and recovery when quorum is lost.