Terabytes → Petabytes Scale
1,000 TB = 1 PB. Your team just crossed the petabyte threshold. That is not a vanity metric — it changes your backup strategy, storage tiering, and cloud egress bill. Scale the numbers before your CFO asks why the S3 line item tripled.
Bidirectional Storage Scaler
TB to PB scale conversion in both directions. Fleet-aggregated storage math for the moment your NAS array becomes a datacenter line item.
Datacenter Storage Reference
Real-world storage configurations at each magnitude tier.
| Configuration | TB | PB |
|---|---|---|
| Single NVMe SSD | 4 | 0.0039 |
| 1U NVMe Server (24× U.2) | 184 | 0.18 |
| 2U JBOD (60× HDD) | 1,320 | 1.29 |
| Ceph Cluster (10-node) | 11,000 | 10.74 |
| Backblaze Vault | — | ~50 PB |
| AWS S3 Standard (Single Region) | — | Exabytes |
Terabytes vs. Petabytes: The 1024× Factor
Storage vendors quote capacity in decimal terabytes (10¹² bytes), while operating systems report in binary tebibytes (2⁴⁰ bytes). The 1,024 multiplier between TB and PB is the binary standard used by filesystems, volume managers, and RAID controllers — 1 PB = 1,024 TB = 1,125,899,906,842,624 bytes.
When provisioning a 10 PB Ceph cluster, you need at least 10,240 TB of raw capacity before erasure-coding overhead. With 8+3 EC, the usable capacity drops to ~72% of raw — meaning a 10 PB target actually requires ~14.2 PB raw, or ~14,540 TB of physical disk. This tool lets you run those back-of-the-envelope calculations in seconds.