15.06.2026
Hetzner price increase June 2026: CPX and CCX up to +176% - our take
For many - us included - Hetzner was the obvious answer to expensive hyperscalers for years: cheap, solid, operated in the EU. That is exactly...
Shared storage directly on your Proxmox nodes - SME-ready, no expensive SAN, with live migration without copying VM data. We plan the design, build the cluster and take responsibility for operations.
The following are trademarks of their respective owners: Proxmox VE (Proxmox Server Solutions GmbH). WZ-IT is an independent service provider and has no business, partnership, or contractual relationship with these companies. We offer independent migration, installation, hosting, and operations services.
Ceph is not an end in itself. The honest answer depends on node count, budget and whether you actually need shared storage.
The detailed comparison including LVM: Proxmox storage: ZFS, Ceph & LVM compared
A Ceph cluster forgives a lot in operations - but little in design. These six points decide stability and performance before the first byte is written.
Ceph needs at least 10 Gbps - exclusively for storage traffic. High-performance setups separate further: 25+ Gbps Ceph-internal, 10+ Gbps public and 1 Gbps dedicated to Corosync. A single modern NVMe can already saturate 10 Gbps.
The default means: three copies of every object, I/O continues as long as two are available. Cutting down on replicas cuts exactly the redundancy Ceph is built for.
The docs are unambiguous: avoid RAID controllers, use host bus adapters (HBA) instead. RAID logic interferes with Ceph's own redundancy and recovery mechanisms rather than complementing them.
Current recommendation: at least 8 GiB of RAM per OSD, the default is 4 GiB. The old 1 GB per TB rule of thumb is outdated - size by OSD count, not by capacity.
Plan at least one core or thread per Ceph service - on top of your VMs. OSDs also benefit from high clock speeds, not just from many cores.
Proxmox VE 9.2 ships Ceph Squid 19.2.3 and Tentacle 20.2.1 - new installations default to Tentacle. The version choice belongs in the planning phase, not in the aftermath.
If an OSD fails, Ceph redistributes the data on its own. Important in operations: wait until the rebalance has finished and enough replicas exist again before intervening further.
The nearfull_ratio warns at 85% by default - a Ceph cluster should be planned well below that capacity-wise and monitored continuously.
EC yields more usable capacity - for the price of performance. RBD on EC pools additionally requires a replicated pool for metadata. An expert topic, not a default setup.
OSD, MON and pool health are onboarded to our highly available Zabbix cluster - we see anomalies before they become incidents.
Ceph and PVE updates coordinated, node by node, with an eye on cluster state - never all at once, never blind.
Ongoing Ceph operations are part of our Managed Proxmox Advanced and Enterprise packages: monitoring of OSD, MON and pool health, updates in maintenance windows, capacity planning and incident response - Managed Proxmox from €179.90 per node per month.
View Managed ProxmoxWe see these five patterns again and again when auditing existing Ceph clusters - each one costs stability, performance or both.
Ceph and Corosync on the same network - Corosync needs low latency; if it shares the wire with storage traffic, I/O load endangers cluster communication.
RAID controllers underneath the OSDs - exactly what the Ceph docs advise against. Use HBAs and leave redundancy to Ceph.
size 2 instead of 3 „to save space“ - undermines the redundancy Ceph is built for and turns every failure into a risk.
Cluster regularly above 85% fill level - beyond the nearfull_ratio, things get tight for recovery and rebalancing.
10 Gbps network shared with VM traffic - the docs require the Ceph network to be exclusive; a single modern NVMe can saturate the link on its own.
We audit existing Proxmox and Ceph environments in a structured health check - network, replication, fill levels, hardware - and take over operations afterwards if desired. Even without documentation.
In-depth knowledge from our Proxmox knowledge base.
15.06.2026
For many - us included - Hetzner was the obvious answer to expensive hyperscalers for years: cheap, solid, operated in the EU. That is exactly...
24.05.2026
Proxmox VE 9.2 has been available since May 21, 2026. On paper, it is a minor release. In practice, it matters much more for many...
05.05.2026
With Proxmox Backup Server 4.2 (released late April 2026), S3-compatible object storage is officially supported as a backup backend. No more tech preview label, no...
The minimum is three nodes - which matches the requirement for Proxmox HA clusters (at least 3 nodes plus shared storage). Three nodes allow the replication default of size 3 / min_size 2: three copies of every object, with I/O continuing as long as two are available. More nodes improve fault tolerance, rebalancing behavior and capacity.
They are different tools. Ceph is shared storage for 3+ nodes: live migration without copying VM data, self-healing, scale-out. ZFS is local storage - for 2-node setups or smaller environments combined with storage replication (pvesr): ZFS-only, asynchronous, minimum interval 1 minute, and the latest state may be lost on failover. If you want true HA with shared storage, you end up with Ceph; if you run 2 nodes, with ZFS plus replication.
At least 10 Gbps exclusively for Ceph traffic - sharing with VM or Corosync traffic is not an option, especially since a single modern NVMe can saturate 10 Gbps. High-performance setups separate further: 25+ Gbps for the Ceph-internal network, 10+ Gbps public and 1 Gbps dedicated to Corosync.
Yes, provided the hardware fits: at least 3 nodes, dedicated disks for the OSDs on HBAs (no RAID controllers), sufficient RAM (at least 8 GiB per OSD recommended) and an exclusive network with at least 10 Gbps. In practice, the network is the most common retrofit effort - which is exactly what we assess upfront during planning.
Ceph heals itself: the affected OSD goes down and the data is redistributed from the remaining replicas. With size 3 / min_size 2, I/O continues in the meantime. It is important to wait until the rebalance has finished and enough replicas exist again before further intervention - for us, that is part of the monitored standard procedure.
Yes. Ceph operations are part of our Managed Proxmox packages Advanced and Enterprise: monitoring of OSD, MON and pool health via our highly available Zabbix cluster, updates in maintenance windows, fill-level and capacity planning as well as incident response - Managed Proxmox from €179.90 per node per month.
Good choice - we'll help you get started or with operations.
These solutions are often used together with Proxmox
These solutions offer similar functionalities and can be evaluated together
No risk: worst case, you leave with a clearer understanding of your project than before.


“WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.”
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.
Timo Wevelsiep & Robin Zins
Managing Directors of WZ-IT

