Sprint 4C · Cornerstone calculator
Proxmox Infrastructure Calculator: Backup, Network & HA
A Proxmox infrastructure plan fails when storage, networking, backup and power are sized independently. This calculator combines PBS repository capacity, migration bandwidth, UPS screening and HA topology so the recommendation exposes cross-system bottlenecks before you start buying parts.
Quick answer
What should a complete Proxmox infrastructure plan include?
At minimum, size a recoverable PBS repository, a network that can meet backup and migration windows, power protection that keeps shutdown dependencies alive, and a quorum/storage architecture that matches the availability objective. Then verify each subsystem with measurements after deployment.
Live Amazon hardware
Live infrastructure hardware
The catalogue shows representative PBS hosts, storage, NICs, switches and UPS systems in separate groups. Current prices and listings support the buying decision without mixing product classes.
Buying decision
One calculator should not hide its assumptions
This tool intentionally exposes simple conservative formulas instead of pretending to predict dedupe ratios, Ethernet efficiency, battery curves or failover time. Use it to identify the part of the design that deserves deeper validation.
Interactive planner
Proxmox Backup, Network & HA Calculator
Enter node count, protected VM data, change rate, migration goal, Ceph use and UPS load to build a first infrastructure plan.
Outputs are planning screens. Confirm PBS retention/dedupe statistics, measured link throughput, UPS runtime curves and cluster failure behavior before deployment.
Compatibility checkpoints
Check these constraints before buying hardware
Quorum
A cluster needs a majority to make safe decisions. Two-node designs require a deliberate quorum strategy such as a QDevice rather than wishful thinking.
Corosync quality
Cluster communication values low latency and reliability. A dedicated physical path is preferable when production traffic could congest the same links.
Guest storage
A surviving node can only recover a guest when its required storage is available there through shared or appropriately replicated storage.
Power and network diversity
Three compute nodes on one switch and one UPS still share major failure domains. High availability is an end-to-end architecture, not a node count.
Start with recovery before performance
The combined model in Proxmox Infrastructure Calculator uses start with recovery before performance to connect a PBS repository that survives primary-host failure with the rest of the infrastructure. Fast VM storage is useful, but infrastructure planning begins with the ability to restore when that storage or host is gone. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat start with recovery before performance as a checkpoint that should be recalculated after meaningful growth. Separate the backup failure domain and confirm the repository has enough capacity for realistic retention before optimizing migration speed. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Translate VM data into repository size
The combined model in Proxmox Infrastructure Calculator uses translate vm data into repository size to connect protected baseline, daily churn and retention with the rest of the infrastructure. The model uses a conservative changed-data reserve rather than assuming a magical dedupe percentage. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat translate vm data into repository size as a checkpoint that should be recalculated after meaningful growth. After PBS has real statistics, replace planning factors with observed growth and rerun the infrastructure decision. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Translate migration size into bandwidth
The combined model in Proxmox Infrastructure Calculator uses translate migration size into bandwidth to connect gigabytes that must move inside a maintenance window with the rest of the infrastructure. A target such as moving 300 GB in ten minutes makes the minimum payload rate visible. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat translate migration size into bandwidth as a checkpoint that should be recalculated after meaningful growth. Compare that requirement with 2.5, 10 and 25GbE only after confirming source and destination storage can feed the link. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Treat Ceph as additional network demand
The combined model in Proxmox Infrastructure Calculator uses treat ceph as additional network demand to connect replication, recovery and client I/O competing for links with the rest of the infrastructure. Distributed storage can make network design part of the storage design, especially during recovery. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat treat ceph as additional network demand as a checkpoint that should be recalculated after meaningful growth. Do not size a Ceph-capable network solely from normal client throughput; consider rebuild and replication traffic as well. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Keep management reachable
The combined model in Proxmox Infrastructure Calculator uses keep management reachable to connect an independent path during network changes with the rest of the infrastructure. A high-speed migration network is not useful if a bridge or bond error removes administrator access to the host. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat keep management reachable as a checkpoint that should be recalculated after meaningful growth. Maintain console or alternate management access until the new network and VLAN design has been proven. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Build UPS scope around dependencies
The combined model in Proxmox Infrastructure Calculator uses build ups scope around dependencies to connect compute, storage and network devices needed for clean shutdown with the rest of the infrastructure. Protecting only the server can leave guests stranded when shared storage or switches lose power first. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat build ups scope around dependencies as a checkpoint that should be recalculated after meaningful growth. Add the watts of every device required by the shutdown and recovery procedure before checking UPS capacity. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Use quorum as an architecture input
The combined model in Proxmox Infrastructure Calculator uses use quorum as an architecture input to connect number of nodes and voting design with the rest of the infrastructure. Three nodes make majority quorum straightforward, while two-node systems require a QDevice or another deliberate strategy. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat use quorum as an architecture input as a checkpoint that should be recalculated after meaningful growth. Quorum does not create spare compute or storage copies, so evaluate those resources separately. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Reserve compute capacity for failure
The combined model in Proxmox Infrastructure Calculator uses reserve compute capacity for failure to connect guest restart after one node disappears with the rest of the infrastructure. An HA cluster cannot restart everything if the surviving nodes have no CPU or RAM headroom. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat reserve compute capacity for failure as a checkpoint that should be recalculated after meaningful growth. Model the worst protected node loss and make sure the remaining machines can carry the workloads that actually need HA. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Separate shared failure domains
The combined model in Proxmox Infrastructure Calculator uses separate shared failure domains to connect switches, UPS units, storage shelves and site power with the rest of the infrastructure. Redundant servers often remain connected to the same single point of failure. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat separate shared failure domains as a checkpoint that should be recalculated after meaningful growth. Draw the dependency diagram and mark every component whose failure stops all nodes; those marks reveal the next resilience investment. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Use current product data cautiously
The combined model in Proxmox Infrastructure Calculator uses use current product data cautiously to connect marketplace price and model evidence with the rest of the infrastructure. The live catalogue helps compare hardware classes, but seller claims do not validate firmware, battery condition or transceiver interoperability. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat use current product data cautiously as a checkpoint that should be recalculated after meaningful growth. Verify the exact delivered model and run burn-in tests before the new component becomes part of the recovery path. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Measure after deployment
The combined model in Proxmox Infrastructure Calculator uses measure after deployment to connect backup throughput, restore throughput, migration time and UPS behavior with the rest of the infrastructure. Planning estimates are most valuable when they are replaced by real observations. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat measure after deployment as a checkpoint that should be recalculated after meaningful growth. Record actual results in the infrastructure document and adjust schedules or hardware before growth turns a small bottleneck into an outage problem. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Revisit the plan after every major change
The combined model in Proxmox Infrastructure Calculator uses revisit the plan after every major change to connect new workloads, storage pools, switches or retention rules with the rest of the infrastructure. Infrastructure is a system of coupled constraints, so one upgrade can move the bottleneck somewhere else. Backup, networking, power and HA constraints interact, so one oversized component cannot compensate for a weak recovery path elsewhere. Keep each assumption visible and trace it to an operational objective.
Treat revisit the plan after every major change as a checkpoint that should be recalculated after meaningful growth. Re-run the calculator when capacity or service objectives change and keep the architecture aligned with the environment you actually operate. Replace estimates with measured backup rates, migration times, repository growth and outage tests as those data become available. The updated figures show which subsystem should receive the next dollar of budget.
Questions people ask
Proxmox Infrastructure Calculator questions
What does the Proxmox infrastructure calculator size?
It combines a PBS capacity target, network class, UPS screening requirement and HA/quorum direction from the inputs you provide.
Does the calculator predict PBS deduplication?
No. It deliberately uses conservative capacity assumptions rather than claiming a universal dedupe ratio.
Does it guarantee 10GbE migration time?
No. The network estimate assumes payload efficiency, while source and destination storage, CPU and protocol overhead can reduce real throughput.
Can it choose an exact UPS runtime?
No. It calculates an energy and VA screening target; actual runtime must come from the manufacturer curve at the measured load.
Why does node count matter?
Node count affects quorum and how much capacity survives a host failure. Three nodes are the straightforward majority-quorum foundation for HA.
Why does Ceph affect the network recommendation?
Ceph uses network bandwidth for client I/O, replication and recovery, so distributed storage can make link headroom more important.
Should PBS be on the same cluster?
A separate physical PBS system gives stronger recovery independence when the protected cluster is down. Co-located designs can be useful for labs but share more failure modes.
Is 25GbE required for HA?
No. HA needs reliable cluster communication and accessible guest storage. Link speed should be driven by migration, storage and recovery workloads.
What live products does this page show?
It can show PBS host candidates, repository drives, NICs, switches and UPS systems from the dedicated Sprint 4C catalogue.
What should I verify after building?
Run a real backup and restore, time a representative migration, simulate power-loss shutdown safely, and test cluster maintenance/failover behavior.
Official references and methodology
Verify the current Proxmox and hardware requirements before deployment
The cornerstone tool combines deliberately conservative planning models for backup, networking, UPS and HA. It exposes assumptions and links to the deeper guides instead of presenting a single synthetic score as certainty.
- Proxmox Backup Server system requirements
- Proxmox Backup Server storage documentation
- Proxmox Backup Server FAQ
- Proxmox Backup Server maintenance
- Proxmox VE network configuration
- Proxmox VE cluster manager
- Proxmox VE HA manager
- Proxmox VE cluster manager
- Proxmox VE network configuration
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, firmware, transceiver compatibility, link capabilities, switch features, UPS runtime, battery condition and seller terms can change. Verify the exact delivered model and your platform documentation before deployment.