Windows 11 · How-To
Windows Storage Spaces: Pool Your Drives for Backup and Redundancy
Windows Storage Spaces lets you glue two or more drives — even mismatched sizes and brands — into one storage pool, then carve a virtual drive called a storage space out of it with the redundancy you choose. In Windows 11 you set it up under Settings > System > Storage > Advanced storage settings > Storage Spaces. Pick a two-way mirror if you want the pool to shrug off one failed drive, and keep reading for the one caution that matters most: this is redundancy, not a backup.
If that framing sounds familiar, it should. Storage Spaces is the modern, first-party heir to Windows Home Server Drive Extender — the beloved feature that first let ordinary people pool a pile of spare drives and stop caring which disk a file landed on. Drive Extender was dropped after Windows Home Server 2011, and Storage Spaces is where that idea lives on. This guide walks through what a pool is, what each resiliency type actually protects against, how to create one in Windows 11, and where the honest limits are.
What a storage pool and a storage space actually are
There are two layers, and keeping them straight makes everything else click:
- A storage pool is the raw material — the physical drives you hand to Windows. Once a drive joins a pool it stops behaving like a lettered volume; its capacity is absorbed into the pool's total. You can add more drives to a pool later to grow it.
- A storage space is a virtual drive you create from a pool. It gets a drive letter and behaves like any normal disk to Windows and your apps, but underneath, Windows spreads its data across the pooled physical drives according to the resiliency you chose.
That separation is what gives Storage Spaces its flexibility. The pool can be a jumble of a 4 TB drive, a 2 TB drive and an old 1 TB drive over USB; the space you present to Windows is one tidy volume with a single letter. Microsoft's Storage Spaces overview on Microsoft Learn describes the same two layers: physical drives aggregated into a single logical storage pool, from which you carve virtual disks known as Storage Spaces.
Resiliency types: what each one protects against
When you create a space, Windows asks for a resiliency type. This is the single most important decision, because it decides how many drive failures the space can survive and how much of your raw capacity you keep. Here is the plain-English breakdown.
| Resiliency | Min. drives | Survives | Capacity cost | Best for |
|---|---|---|---|---|
| Simple | 1 | Nothing — a single drive failure loses the space | None (all usable) | Scratch files, temp data you can lose |
| Two-way mirror | 2 | One drive failing | ~50% (two copies) | The sensible home default |
| Three-way mirror | 5 | Two drives failing at once | ~66% (three copies) | Higher-stakes data, more drives |
| Parity | 3 | One drive failing (single parity) | Low overhead, more usable space | Large, mostly-read archives & backups |
Simple (no resiliency)
Data is striped across the drives for speed and maximum capacity, with no redundancy. It is fast and wastes nothing, but if a single drive dies the whole space is gone. Only use Simple for data you are genuinely willing to lose — a video scratch disk, a cache, a download staging area.
Two-way and three-way mirror
Mirror spaces keep two or three copies of your data on different physical drives. A two-way mirror keeps two copies and survives one drive failing; it needs at least two drives and gives you roughly half your raw capacity as usable space. A three-way mirror keeps three copies, survives two drives failing simultaneously, and needs at least five drives — those minimums come straight from Microsoft Support's Storage Spaces in Windows page, which puts a two-way mirror at two drives tolerating one failure and a three-way mirror at five drives tolerating two. Mirrors have the best write performance of the resilient options, which is why a two-way mirror is the right default for most people protecting documents, photos and media libraries.
Parity
Parity stripes your data across drives along with parity information that lets Windows reconstruct a failed drive's contents, much like RAID-5. It needs at least three drives, survives one drive failing, and is far more space-efficient than a mirror — you lose roughly the capacity of one drive rather than half the pool. The tradeoff is slower writes, because parity has to be calculated on every write. That makes parity a good fit for large archives and backup targets you read far more often than you write, and a poor fit for busy, write-heavy workloads. Microsoft Learn reaches the same conclusion, listing parity spaces as more storage-efficient than mirrors but with lower write performance due to parity calculations, and ideal for archival storage and backups.
A mirror or parity space protects you against exactly one thing: a drive dying. It does nothing about the risks that lose most people's files. Delete a file by mistake and it vanishes from every copy instantly. A file corrupts, ransomware encrypts your library, the PC is stolen, a surge fries the whole box — the redundant copies live in the same machine, so they all go together. Storage Spaces keeps you running when hardware fails; a separate backup on other media or in the cloud keeps you safe when something worse happens. Run both. This is the same lesson Drive Extender taught a generation ago, and it has not changed.
Thin provisioning: creating a space bigger than your drives
When you create a space, Windows lets you set a size larger than the physical capacity currently in the pool. This is thin provisioning: the space claims a big logical size up front, but Windows only consumes real disk as you actually write data. When the pool starts filling up, Windows warns you, and you add another drive to the pool to keep going. It is a genuinely useful way to plan for growth — but it is not free space. Once the physical drives are full, the thin-provisioned space stops accepting writes until you feed the pool more drives.
How to create a storage pool and space in Windows 11
The modern path lives in the Settings app. (In older Windows 10 builds, and still today, you can do the same thing from Control Panel — see the note after the steps.)
Adding a drive to a pool erases anything on it. Copy off any files you need first. You want at least two drives for a mirror or three for parity, and it is fine for them to be different sizes. An administrator account is required.
- Press
Windows + Ito open Settings. - Go to System > Storage.
- Expand Advanced storage settings, then click Storage Spaces.
Settings > System > Storage > Advanced storage settings > Storage Spaces - Click Add (or Create a storage pool), give the pool a name, tick the drives you want to include, and confirm to create the pool.
- Windows then prompts you to create a storage space from the new pool. Give the space a name and pick a drive letter and file system (NTFS for general use; ReFS is available on supported builds).
- Choose your resiliency type — Simple, Two-way mirror, Three-way mirror or Parity — using the breakdown above.
- Set the size. You can accept the suggested size or enter a larger one to take advantage of thin provisioning.
- Click Create. The space appears in File Explorer as a normal drive with the letter you chose, ready to use.
To grow a pool later, return to the same Storage Spaces screen, open your pool, and use Add drive. To adjust or optimise how data is spread after adding a drive, use the pool's properties on the same screen.
The older Control Panel applet is unchanged and offers a few options the Settings page keeps simpler, such as choosing parity explicitly and managing physical drives in detail. Open it from the Run box:
control /name Microsoft.StorageSpacesOn Windows 10 this Control Panel route (Control Panel > System and Security > Storage Spaces) is the primary way in; the Settings-app page above is the Windows 11 front end for the same underlying feature. Exact button labels can shift between Windows builds, so if a wording differs on your PC, look for the equivalent Create / Add control on the Storage Spaces screen.
A few honest cautions before you commit
- Mirrors cost you half. A two-way mirror of two 4 TB drives gives you about 4 TB of usable, protected space — not 8. Plan capacity around that, not the raw total.
- Parity is slow to write. It is excellent for an archive you fill once and read often; it is frustrating as a working drive for large, frequent writes.
- USB drives can be flaky pool members. Storage Spaces will happily pool external USB disks, but a sleeping or briefly disconnected USB drive can drop out of the pool. Internal SATA/SAS drives make for a far more dependable pool.
- Replace failed drives promptly. Redundancy only helps until the next drive fails. A two-way mirror running on a single surviving drive has no protection left, so swap a dead drive in quickly and let the pool rebuild.
- Still keep a real backup. Worth repeating: pool, then back the pool up somewhere else.
This topic goes back a long way on windows-now.com. The idea of pooling mismatched drives into one growing volume was first covered here in the windows-now.com era by Doug Knox, who pointed readers at Microsoft's technical brief on Windows Home Server Drive Extender — the feature Storage Spaces effectively replaced. If you enjoy the history behind today's tool, read the original archived post.
For more current walkthroughs like this one, browse our How-To Guides. If you are curious how the same drive-pooling problem was solved in the home-server era, the windows-now.com archive is full of it, and our Home Server guides pick up the theme.
Frequently asked
Is Storage Spaces a backup?
No. A mirror or parity space keeps redundant copies on separate drives inside the same PC, so it survives a drive failing. It does nothing about the risks that actually lose most people's files: an accidental delete, a file that corrupts, ransomware, theft, fire or a power surge that takes the whole machine. Every one of those hits all copies at once. Treat Storage Spaces as uptime insurance against a dead drive and keep a genuine backup on separate media or in the cloud for anything you cannot afford to lose.
Can I mix drives of different sizes and brands in a storage pool?
Yes. That flexibility is the whole point of Storage Spaces, and it is what made it the spiritual heir to Windows Home Server Drive Extender. You can pool SATA, USB and SAS drives of different makes, sizes and ages into one pool, and add more drives later to grow it. Bear in mind that with mirror and parity resiliency the usable capacity depends on how the copies are laid out, so a pool of mismatched sizes will not always yield every last gigabyte as protected space.
Which resiliency type should I choose?
For most home and small-office setups that hold anything you care about, a two-way mirror is the sensible default: it survives one drive failing and needs only two drives. Choose a three-way mirror (five drives) if you want to survive two drives failing at once. Parity suits large, mostly-read archives and backup targets where you want more usable capacity and can accept slower writes. Use Simple only for scratch data you are willing to lose, because a single drive failure destroys a Simple space.
What is thin provisioning and can I create a space bigger than my drives?
Thin provisioning lets you create a storage space with a logical size larger than the physical capacity currently in the pool. Windows only consumes real disk as you write data, and warns you when the pool is running low so you can add another drive. It is handy for planning ahead, but the space stops accepting writes once the physical drives fill up, so it is a convenience, not free capacity.