Understanding Storage Capacity

Akins IT • November 20, 2022
Connect with us

Storage capacity refers to how much disk space one or more storage devices provides. It measures how much data a computer system may contain. For an example, a computer with a 500GB hard drive has a storage capacity of 500 gigabytes A network server with four 1TB drives, has a storage capacity of 4 terabytes. Storage capacity is often used synonymously with "disk space." However, it refers to overall disk space, rather than free disk space. For example, a hard drive with a storage capacity of 500GB may only have 150MB available if the rest of the disk space is already used up. Therefore, when checking your computer to see if it meets a program's system requirements, make sure you have enough free disk space to install the program. If you need more disk space, you can increase your computer's storage capacity by adding another internal or external drive.


Storage capacity is an important factor when deploying infrastructure in the data center. Storage vendors describe capacity in different ways, and it’s essential that you know how to interpret them properly for sizing the infrastructure that your organization really needs, and for comparing the cost of capacity (cost divided by gigabytes) between different storage systems. However, interpreting the capacity of modern storage systems can be surprisingly tricky. Different vendors use wildly different metrics to advertise the capacity of their systems, including:


Raw Capacity


This is the total capacity of the storage media in the system. For example, if your system contains 20 drives at 5TB each, the raw capacity is 100TB. Vendors sometimes mistakenly price their systems based on raw capacity, but users should focus on usable capacity instead because usable capacity can be significantly lower than raw capacity. That is why raw capacity is generally reported in decimal terabytes.


Usable Capacity


This is how much data can be stored in the system in the absence of any data reduction, meaning before data reduction. The use of the term usable capacity is to mean capacity before data reduction. Usable capacity is lower than raw capacity beacuse of overheads such as RAID (redundant array of independent disks) and flash over-provisioning. The ratio of the usable capacity to the raw capacity is referred to as the “usable ratio”, which by definition is usauble capacity divided by raw capacity is greater or equal to one.



Usable Capacity / Raw Capacity = Usable Ratio


Effective Capacity with Data Retention


This is how much data can be stored in a system (after data reduction) assuming some amount of data reduction using techniques such as compression and deduplication that reduce the amount of space used by a dataset. Effective capacity is generally higher than usable capacity. The ratio of the space used by a dataset without any reduction and the space used by the dataset after reduction is called data reduction ratio, which by definition is greater than or equal to one. If a system employs multiple techniques for data reduction, the total reduction ratio is the product of the technique-specific reduction ratios.


In conclusion, modern storage systems involve a complex tradeoff between capacity, reliability, and performance, so in addition to storage capacity one must also be aware of the reliability and performance characteristics of a system. Storage capacity can be a mundane subject, but paying close attention in this area will enable you to select storage systems and size them optimally to match your requirements and budget.

CONTACT US IF YOU HAVE MORE QUESTIONS

Storage Whitepapers

By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts