FlashSystem Sizing and Usable Capacity
How to think about raw, usable, and effective FlashSystem capacity before requesting an IBM storage quote.
A FlashSystem quote can look right and still be wrong if raw, usable, and effective capacity are mixed together. Buyers should define the capacity basis before comparing models or vendors.
Capacity terms buyers should separate
| Term | What It Means | Why It Changes the Decision |
|---|---|---|
| Raw capacity | Total physical media capacity before RAID, sparing, metadata, and overhead. | Useful for hardware inventory, not enough for application sizing. |
| Usable capacity | Capacity available after protection and system overhead. | The right starting point for workload placement and growth planning. |
| Effective capacity | Usable capacity after assumed compression or deduplication. | Can be valid, but should be tied to observed data patterns or IBM's guarantee assumptions. |
| Protected capacity | Capacity after snapshots, Safeguarded Copy, replication, and DR copies. | Often the number that exposes whether the quote is underbuilt. |
Sizing Questions Before a Quote
Workload mix
Separate IBM i database, VMware, file services, backup, and analytics workloads before applying any reduction ratio.
Change rate
Snapshot and Safeguarded Copy capacity depends on changed data over time, not only total live data.
Replication
A second site, third copy, or Cyber Vault can change the protected capacity requirement more than the model name does.
Growth window
Define whether the system must cover 12 months, 36 months, or a full lifecycle program before adding drives.
A 20 TB to 30 TB environment may fit more than one FlashSystem tier. The correct answer depends on latency, growth, snapshot retention, host count, replication, and whether the data reduction assumption is realistic for the workload.