The Ultimate Budget Proxmox Home Lab Tour: Building a 3-Node Cluster
When most people picture a home lab, they imagine a massive 42U server rack, jet-engine fans screaming in a basement, and an electricity bill that rivals a small factory.
Here’s the reality: you do not need enterprise rack servers to build a resilient, high-availability self-hosted environment. In fact, for hobby developers, homelab beginners, and self-hosters, big rack servers are often a huge trap—they draw 300+ watts of power at idle, generate massive heat, and take up huge amounts of physical space.
In this architecture tour, we’re breaking down my 3-node Proxmox VE cluster. Built entirely from cheap, refurbished Dell OptiPlex mini desktops picked up on eBay, this entire setup cost less than a single mid-range graphics card, runs whisper quiet on a corner of my desk, and pulls less than 45 watts total at idle.
Let's walk through the hardware choices, network segmentation over a managed switch, Ceph hyper-converged storage, Linux Containers (LXCs), and automated nightly disaster recovery with Proxmox Backup Server (PBS).
1. The Hardware: Why Dell OptiPlex Desktops are the Sweet Spot
The foundation of this budget cluster is three refurbished Dell OptiPlex 9020 small-form-factor / micro units. Why choose off-lease office PCs over custom mini PCs or Raspberry Pis?
- Unbeatable Value: Corporations dump thousands of these onto eBay and local liquidators every month. You can routinely find them for $60 to $90 each with an Intel quad-core processor and power brick included.
- x86 Compatibility: Unlike ARM boards (like Raspberry Pis), x86 Intel CPUs run every Docker container, VM image, and Linux distribution without compatibility issues.
- Expandability: Standard SATA drive bays, M.2 slots (or PCIe adapter options), and dual DDR3/DDR4 RAM slots that easily scale up to 16GB or 32GB per node.
- Low Power & Silence: Idle power draw is around 12 to 15 watts per machine. The entire 3-node stack consumes less power than a single traditional light bulb.
2. The 3-Node Rule: Why You Need 3 Nodes (Not 2)
A common mistake beginners make is buying two mini PCs and trying to create a cluster.
In Proxmox VE (and clustering systems in general), clusters rely on Quorum to make decisions. Quorum is a simple mathematical vote: a cluster is only healthy if more than 50% of the nodes agree on the state of the system (the 2n + 1 rule).
If you have only 2 nodes and one network cable gets unplugged, each node thinks the other node is dead. Because neither node has more than 50% of the vote (each has exactly 50%), the cluster enters a "split-brain" state and freezes all virtual machines to prevent data corruption.
With 3 nodes, if Node 1 goes down or reboots for kernel updates, Node 2 and Node 3 still have 2 out of 3 votes (66%), allowing your services to stay online with zero downtime!
3. Network Segmentation & VLANs: Keeping Traffic Clean
To prevent storage sync traffic from choking out regular home network devices, all three nodes connect through an 8-Port Managed Smart Switch segmented into three distinct VLANs:
- VLAN 0 (Personal Home Network): The default, untagged native network for personal everyday devices—family laptops, smartphones, streaming boxes, and smart TVs.
- VLAN 100 (Home Lab Network): The dedicated playground for our Proxmox nodes, management web interface (port 8006), LXC containers, virtual machines, and self-hosted developer tools.
- VLAN 200 (Ceph Backend Storage Highway): An isolated, high-speed network purely dedicated to Ceph backend storage traffic, cluster replication, and disk sync between nodes without competing with regular LAN bandwidth.
4. Storage: Hyper-Converged Redundancy with Ceph & ZFS
Traditional home labs rely on a separate Network Attached Storage (NAS) box running TrueNAS or Synology. The risk? If your single NAS crashes or loses power, every single compute server loses its hard drives.
With Proxmox VE, you can use Ceph or ZFS Storage Replication to create hyper-converged storage. This pools the SSDs inside all three Dell OptiPlex machines into a single unified storage pool. If an entire computer suddenly dies, the virtual disk image is already replicated on the other two nodes, allowing Proxmox to automatically spin the workload back up in seconds.
5. VMs vs. LXCs: The Secret to Maximum Density
When running on older or budget hardware, RAM is your most precious resource.
A full Virtual Machine (VM) must emulate an entire virtual hardware motherboard, CPU, BIOS, and dedicated operating system kernel. A simple Ubuntu Server VM running Pi-hole will happily consume 1GB to 2GB of RAM just idling.
Linux Containers (LXCs) share the host Linux kernel directly while providing isolated root environments. An LXC container running Pi-hole or Nginx uses as little as 35MB to 60MB of RAM!
By converting 80% of our homelab services into lightweight LXC containers, our 48GB cluster easily runs 25+ simultaneous isolated services with RAM to spare. (See our Pi-hole Proxmox LXC Guide for a step-by-step example).
6. Disaster Recovery: Nightly Backups with PBS
The greatest benefit of a home lab is having a sandbox where you can learn by breaking things. But that only works if you can restore a broken container in 30 seconds.
We run an instance of Proxmox Backup Server (PBS) on an external USB hard drive or secondary backup target. PBS utilizes block-level deduplication and incremental backups. Every night at 3:00 AM, Proxmox snapshots every container and VM. Because it only copies newly changed data blocks, 25 container backups complete in under two minutes!
"If an update goes wrong or you accidentally delete a configuration file, you can roll back to last night's snapshot in a single click."
Summary: Start Small, Think Resilient
You don’t need an enterprise budget or a data center rack to learn enterprise-grade virtualization, networking, and high availability. Three cheap refurbished Dell OptiPlex desktops, an inexpensive managed switch, and Proxmox VE give you a resilient, quiet, and power-efficient playground that will teach you more about modern infrastructure than any simulator.
Ready to deploy your first container? Check out our guides on Docker vs. Podman and Setting Up Cloudflare Zero Trust Tunnels.