Storage Space vs Disk Management Mirroring

Posted on

A server stack is the collection of software that forms the operational infrastructure on a given machine. In a computing context, a stack is an ordered pile. A server stack is one type of solution stack — an ordered selection of software that makes it possible to complete a particular task. Like in this post about Storage Space vs Disk Management Mirroring was one problem in server stack that need for a solution. Below are some tips in manage your windows server when you find problem about windows, raid, , , .

Windows 2012 R2:

I am deciding on a RAID 1 (Mirroring in Windows terminology) implementation. I understand I have two options included in Windows:

  • Storage Space Mirroring
  • Disk Management Mirroring

How does Storage Space compare Mirroring to Disk Management Mirroring?

I have made some benchmarking on my home lab server using both technologies with two Samsung 850 PRO 512GB.

From what I can see, both mechanisms work the same way. Storage Spaces Mirroring performs better but consumes more CPU under diskspd benchmark, Dynamic Volumes Mirroring is a bit slower and obviously less CPU hungry.

Hope this helps you to decide what to go with.

I just wanted to ask the same question, after doing some tests of my own, here are my findings.

I am not using SSDs but rather standard HDs.

Using the disk managagement mirroring seems to be a little faster. I used queue depth of 8 and came up with values for blocksize 512B, 8KB, 64KB and 4M in Atto Benchmarking Tool:

10M/15M, 140M/155M, 202M/200M, 200M/201M plain disk, only 1 partition

9M/20M, 140M/200M, 200M/200M, 200M/395M plain mirror in disk management, only 1 partition

7M/12M, 133M/151M, 200M/204M, 201M/377M storage pool storage space on first partition, others are a little slower

But.. to me that is neglible, since real performance depends on random I/O (where performance is more similar) and also if you access/share the drives through 1GBit/s network, in which case there is a limit at a little over 100MB/s anyway.

Most important for mirroring is the (rare) error case. So I also googled how to restore a broken mirror. There seems to be a large difference – for whatever reason.

Recovery seems very complicated for storage pool/storage spaces mirror:

https://technet.microsoft.com/en-us/library/dn782852%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396

For disk management mirror it seems a lot easier

https://technet.microsoft.com/en-us/library/cc938519.aspx?f=255&MSPPError=-2147217396

So: disk management way was slightly faster (for me, on Windows Server 2016), plus recovery looks a lot easier. I did not use any cache-size tweaking or anything similar.

I also did not compare CPU usage, since I assume that high CPU and high I/O won’t go together very often.

Originally, I also wanted to compare Starwind Virtual SAN and mirror across servers (creating a cluster) but I guess local mirror with backups will be good enough and the performance comparison with that is useless due to network bottleneck.

There is one big difference between “Disk Management” mirrored disks and “Storage Spaces”. “Disk Management” is better from space utilization perspective, but not as flexible when physical storage needs to grow over time.

Assuming 2-disks are of the same size. Assuming “Disk Management” would use “Mirrored Mode” and “Storage Spaces” uses 2-way mirror.

Disk Management

PRO: Disk Management will simply duplicate your disk content to the 2nd disk and thus your total space available will be equal to the size of the drive. If you have 2 5TB drives, then you can store 5TB of data.

CON: When you are out of space you are out of space on the disk.

Storage Spaces

PRO: Storage Spaces allows you to allocate more space than currently physically available. When you are physically out of space, you can add 2 new drives of equal size to grow your pool. So, you can start with a couple 5TB and then add a couple 6TB drives and so on.

CON: You loose half of drive storage capacity in 2-way mirroring. If you have 2 5TB drives, then you can store 5TB/2=2.25 (and reduce that to lowest even number): 2.24 TB.

I don’t know if Storage Space volume size can be increased after it is created without loss of data.

Data is based on my personal experience on Windows 10 Pro when I had to answer the same question.

Some additional information not yet mentioned in other answers:

Two reasons to use Storage Spaces over Mirrored Volumes via Disk Management:

  1. If you plan to use BitLocker for encryption, Mirrored Volumes does not support this but Storage Spaces does

  2. If you plan to use Backup and Restore (Windows 7) and you select a Mirrored Volume as the backup destination, you’ll get a warning message along the lines of “When restoring a system image from this volume, the disks on your computer cannot be formatted to match the layout of the disks in the backup”. This warning is not present when using a Storage Space as a backup destination.

Leave a Reply

Your email address will not be published.