kubertpmox
A second, separate Proxmox cluster: nine nodes, all-flash Ceph, and a deliberately lean layout. It exists so that disaster recovery does not depend on the cluster it is protecting.
Why a second cluster
Backups that live inside the system they protect are only half a backup. kubertpmox gives the lab an independent failure domain for VM backups, staging workloads, and disaster recovery. It is smaller and simpler than pmoxprime on purpose: fewer drive classes, fewer pools, fewer moving parts.
What is in it
The cluster runs Proxmox VE 9.1.2 across nine hosts. Ceph uses 13 OSDs — five NVMe and eight enterprise SSD — with a primary ceph_nvme pool at 3/2 replication. CephFS is active with two standby MDS daemons. Backups land on a Proxmox Backup Server on the lab network.
kubert
pmox2096
shinken
pmox2093
pmox2072
pmox2070 / 2071
Cluster summary
| Metric | Value |
|---|---|
| Nodes | 9 (PVE 9.1.2) |
| Total vCPU | ~560 |
| Total RAM | ~2.7 TB |
| Ceph OSDs | 13 (5 NVMe + 8 SSD) |
| Ceph health | HEALTH_OK |
| CephFS | Active, 2 standby MDS |
| Primary pool | ceph_nvme (3/2 replicated) |
| Backups | Proxmox Backup Server on the lab network |
| Corosync | Lab network |
Drive detail
| Node | NVMe | SSD | Notes |
|---|---|---|---|
| kubert | 3× 1 TB 970 EVO Plus | Mixed 1 TB EVO, 480 GB D2CSTK, 860 EVO, 4 TB EVO | Compute heavy lifter |
| pmox2072 | — | 18× 1.2 TB ST1200MM0007 + 4 TB EVO | ZFS local, not Ceph |
| pmox2096 | — | 4× 1.92 TB + 2× 3.84 TB enterprise SSD | Ceph storage node |
| Standard nodes | 1–2× 1.88–2 TB NVMe | 1–2× Samsung EVO | Paired OSD hosts |
Snapshot date
These figures come from the September 2026 cluster survey. Hardware and pool state change; treat this as an architectural description, not live telemetry. The main cluster's status note is kept closer to current.
How it fits with pmoxprime
The two clusters are managed separately and do not share a Ceph quorum, which is the point. pmoxprime is the production-adjacent system with the capacity tiers and the research data. kubertpmox is the smaller all-flash system that can absorb a restore, host a staging copy, or keep services alive if the main cluster is unavailable.
Both clusters are connected to the same 10 GbE lab network and the same operational tooling. The benchmark work on this site focuses on pmoxprime because that is where the heterogeneous storage tiers are; kubertpmox is intentionally uniform.