Storage Spaces is the Windows storage virtualization feature that groups physical drives into a storage pool and carves that pool into virtual disks with a chosen level of resiliency. It was introduced with Windows 8 and Windows Server 2012 and serves as the modern replacement for software RAID built on dynamic disks.
Among Windows storage and file systems features, Storage Spaces sits below the file system and above the physical drives. A virtual disk created in a pool appears to Windows as an ordinary disk that is formatted with NTFS or ReFS, while Storage Spaces decides where each slab of data is placed and how many copies or parity fragments are kept.
How pools, spaces and slabs work
The architecture has three layers. A storage pool is a collection of physical disks of any size and bus type, including SATA, SAS, NVMe and USB on client editions. A storage space, also called a virtual disk, is defined inside the pool with a resiliency type, a size and a provisioning mode. The file system then sits on top of the space.
Storage Spaces does not mirror whole drives. It divides each space into slabs of 256 MB and distributes those slabs and their copies or parity across the drives in the pool. This lets drives of different capacities work together and allows a failed drive to be rebuilt onto free capacity spread across the remaining drives rather than onto one dedicated spare.
Pool configuration is stored on the member drives themselves, so a complete set of pool drives can be moved to another Windows computer of the same or a newer version and the spaces will be recognized there.
Resiliency types and their trade-offs
The resiliency type determines how many drive failures a space survives and how much raw capacity is consumed. Choosing it is the most important design decision, because it cannot easily be changed later without creating a new space and copying data.
| Resiliency type | Minimum drives | Failures tolerated | Capacity efficiency |
|---|---|---|---|
| Simple | 1 | None | 100 percent |
| Two-way mirror | 2 | One drive | 50 percent |
| Three-way mirror | 5 | Two drives | About 33 percent |
| Parity | 3 | One drive | About 67 to 88 percent depending on drive count |
| Dual parity | 7 | Two drives | About 50 to 80 percent depending on drive count |
Mirror spaces deliver the best write performance and are the safe default for active data and virtual machines. Parity spaces are capacity-efficient but slow to write, because each write requires reading and recalculating parity; they suit archives, media libraries and backups that are written once and read often. A simple space offers no protection at all: the failure of any member drive destroys the whole space.
Provisioning, columns and other parameters
Beyond resiliency, several parameters shape capacity behavior and performance. Most of them are visible only through PowerShell cmdlets such as New-VirtualDisk and Get-VirtualDisk, while the graphical tools apply sensible defaults.
| Parameter | Typical setting | What it affects |
|---|---|---|
| Provisioning | Thin on client, fixed or thin on server | Whether capacity is reserved up front |
| Number of columns | Set by drive count at creation | How many drives are written in parallel |
| Interleave | 256 KB default | Stripe size per column |
| File system | NTFS or ReFS | Integrity features and repair behavior |
| Storage tiers | SSD and HDD tiers on server | Hot data on fast media |
Thin provisioning lets a space be larger than the current physical capacity, which is convenient but risky: when the pool runs out of real space, the virtual disk goes offline until drives are added. The column count matters when expanding, because a space with four columns needs drives added in groups that can satisfy four parallel writes.
Storage Spaces compared with alternatives
Windows administrators can protect data with several competing approaches, each with different portability and performance characteristics.
| Approach | Where redundancy lives | Main consideration |
|---|---|---|
| Storage Spaces | Windows software layer | Flexible drive sizes, portable pools |
| Hardware RAID controller | Dedicated controller | Fast, but tied to the controller model |
| Dynamic disks software RAID | Legacy Windows volume manager | Deprecated, less flexible |
| Storage Spaces Direct | Clustered servers with local drives | Datacenter edition, hyperconverged clusters |
| Network-attached storage | Separate appliance | Shared access, network dependency |
Storage Spaces Direct extends the same concepts across two or more clustered servers, pooling their local drives over the network for highly available virtual machine storage. It is a server and cluster feature and is not part of client Windows.
Setting up and maintaining a pool
On Windows 11, pools are managed under Settings, System, Storage, Advanced storage settings, Storage Spaces, while the classic Control Panel tool remains available. Adding a drive to a pool erases its existing contents, so drives must be checked carefully before selection. The system drive itself cannot be part of a pool.
Good maintenance practice includes monitoring drive health, replacing failed drives promptly and running Optimize-StoragePool after adding drives so that existing data is rebalanced across all members. The cmdlets Get-PhysicalDisk and Get-StorageJob show health status and rebuild progress; a space reported as degraded still serves data but has lost redundancy, so a second failure during that window can cause permanent data loss.
- Use mirror resiliency for working data and parity only for mostly read data.
- Avoid USB enclosures that hide drive identity or disconnect during sleep.
- Keep separate backups, because resiliency does not protect against deletion or ransomware.
- Retire a drive before removal so its data is rebuilt elsewhere first.
In everyday language
Storage Spaces lets Windows treat several separate drives as one large container. You can then create a drive inside that container and ask Windows to keep extra copies of your data on different physical disks.
If one disk breaks, the copies on the others keep your files available, and you simply replace the broken disk. It works like storing two copies of important papers in two different cabinets. It does not replace a backup, because deleting a file removes every copy at once.
Seen in the real world
A freelance video editor has a desktop PC with one fast system SSD and four hard drives: two of 4 TB and two of 8 TB. She needs safe storage for active projects and a large archive of finished work.
She creates one pool from the four hard drives and defines a two-way mirror space of 6 TB for current projects and a parity space for the archive. When one 4 TB drive fails a year later, the mirror and parity spaces stay online with a warning. She installs a new 8 TB drive, retires the failed one, and Windows rebuilds the missing copies across the pool. No project files are lost, and her nightly cloud backup remains the second line of defense.