16

These are the document you are looking for:What are columns and how does Storage Spaces decide how many to use? and Storage Spaces - Designing for Performance and Storage Spaces: Understanding Storage Pool Expansion I will start by quoting two things from the articles provided: "Note Storage Spaces in Windows Server 2012 R2 and earlier by default uses ...


13

Your scenario is fine if you are OK with paying loads of money for licensing. You will also need an interconnect fabrics and switch that supports PFC in order to use SMB Direct feature (I assume you would like to use it because of RDMA-capable Mellanox NICs which are awesome). Your drives allow you to create a parity-based capacity tier and add some SSD-...


11

Yes. What happens to Storage Spaces when moving physical disks between servers? Storage Spaces records information about pools and storage spaces on the physical disks that compose the storage pool. Therefore, your pool and storage spaces are preserved when you move an entire storage pool and its physical disks from one computer to another. ...


11

Currently we suggest SCVMM to our customers only in cases of four and more nodes. I can’t tell for sure whether you need SCVMM in your case, but our last customer with four servers and over 100 VMs is almost not using SCVMM. For more information on configuration, these two topics were very helpful for us: https://technet.microsoft.com/en-us/system-center-...


11

Speaking shortly, the deployment sequence looks as following: Deploy necessary WS roles and features Validate the Failover Cluster Create the Failover Cluster Enable Storage Spaces Direct -EnableStorageS2D Create and configure storage pools Example input: New-StoragePool -StorageSubSystemName #CLUSTER_NAME# -FriendlyName #POOL_NAME# -...


11

All on-board caches are completely bypassed in JBOD mode. If you really need to use them you might want to look at a single-disk RAID0 config, which is unsupported but works with S2D as long as you patch "RAID" -> "SAS" BusType in registry. https://livevirtually.net/2014/06/27/configuring-hp-smart-array-p420i-io-controller-for-vsan/ (That's for VMware VSAN ...


11

Windows Parity Spaces are dog slow and (according to Microsoft) aren’t designed for anything except archive workloads. Microsoft keeps trying to improve write performance say implemented log missing from the hardware RAIDs, but lack of the battery-powered write back cache takes away all the fun. You can however try to improve writes by telling Spaces you ...


9

AFAIK you can run storage spaces even from within a HyperV virtual guest so I imagine yes. Use the Set-PhysicalDisk commandlet to set the media type which appears as nothing more than a label (and not an actual physical property): Set-PhysicalDisk -UniqueId <String> –MediaType SSD Set-PhysicalDisk -FriendlyName <String> –MediaType HDD And ...


9

There's very little to zero sense building SoFS based on S2D. Here's why: 1) Datacenter edition everywhere. It's expensive ($6K+), and while for hyperconverged scenario you pay for licensed Windows Server VMs with SOFS you pay for... nothing! There are no VMs to run! 2) Dual-head configuration is possible since TP5 AFAIK, but there's no local ...


8

Engineering is all about choices and trade-offs. If you want speed? Mirror If you favor cost? Parity Neither is better than the other. Ask the SysAdmin that is over budget but has too few users to appreciate the aggregate speed achieved by mirroring, or the SysAdmin that impressed his/her boss by saving money but now the company is going out of ...


8

This postponed write happens because of a a) file system level write-back RAM cache, and b) parity Spaces design, which absorbs all the writes to the internal log initially to avoid “read-modify-write” on the “critical path” dramatic slowdown. When your write is complete file system keeps flushing data in the “lazy writer” worker thread and Spaces keep ...


8

Most NAS snapshots implement copy-on-write, so the snapshot itself initially takes up no space (or next-to-none, there is some overhead). But any block that is changed whilst the file it's part of is snapshotted must be copied. If an entire file is deleted whilst it's still in a snapshot, all those blocks must still be kept. So in your case above, as long ...


8

TL;DR: You can't do that. If you really want to do that you have to use sort of a storage virtualization stack on top of your disks. Something like HPE VSA will use your existing partitioning and allow to expose PART of your storage pool to external consumers.


8

1) There are many ways to skin a cat (c) ... Depending on how you'll chop your disks and how you'll configure system (HDDs + SSDs for cache Vs. mirror accelerated parity etc) you'll get different usable capacity. 2) It's a bad idea to use S2D on only two nodes. It's fragile and every time you'll have one host down for whatever reason (maintenance, unplanned ...


8

Slabs which are file system cluster equivalents are quite big. So yes, you’ll get fragmentation but no, you won’t notice any performance impact. Really.


7

CPU and memory requirements are negligible if you're not using dedupe. Any modern CPU and at least 4GB RAM should be sufficient, assuming we're talking about 1GbE. If you're talking about 10GbE, then hardware matters more, but not because of storage spaces. Obviously the more memory you can add, the more caching can be done, but for low load usage, you don'...


7

ReFS is much like ZFS in general. They both are completely CPU oriented and do not use anything from hardware RAID controllers. Other vendors (for example StarWind with LSFS) are using hardware parity RAID offload if present so it's not clear why Microsoft has neglected.


7

I vote for shared storage. For the case, StarWind Virtual SAN Free seems to be a better option. Microsoft Storage Spaces Direct are more about Enterprise having requirements to underlying storage and Windows Server's licenses. https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/choosing-drives From my perspective, StarWind ...


7

Microsoft recommends % of usable capacity, "2 disks" is too bold statement for say 90 disk JBOD.


7

It's a bad idea to use parity Storage Spaces because: 1) Single parity is dangerous: every time one disk dies and you start a rebuild process there's a heavy load applied to all remaining spindles, so there are great chances you'll get second, now deadly fault. 2) Performance is horrible. I mean it! ZFS has proper journaling and variable sized parity ...


7

I have 4 HDD drives and want to maximize read performance with 1 level of resiliency. You can deploy MSFT's equivalent of RAID10. Please see what columns have to do with redundancy and performance. https://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx#...


7

The considered setup will result in 6 TB of usable capacity and 1 TB of cache per node. You can always check it with this calculator: https://s2dcalc.blob.core.windows.net/www/index.html I would also never trust 2 node s2d to keep mission-critical data. Unfortunately, such a setup is still from perfect and seems not thorougly tested. For the similar case,...


7

ReFS by itself cannot repair corruptions, it is a feature of Storage Spaces. But ReFS will detect them when on files with data integrity stream enabled when reading the corrupted block, or when ReFS data scrubber encounters the corrupted block during its patrol reads. ReFS is a "new" file system and its stability of ReFS for long-term backup repository is ...


6

ReFS (and Storage Spaces Direct from Windows Server 2016 if you care) takes care indeed of some hardware offload features present in Intel Xeon CPUs (they somehow refuse to work if f.e. "popcnt" instruction support is missing) for strong hash summing but it doesn't use anything with XOR and polynomial calculations for RAID6 neither from CPUs nor from ...


6

I have faced exactly the same issue trying to create a 2-node dedicated S2D storage cluster for one of the branch offices. Bus type RAID is a no go and I had to replace the 3108 controllers with some other HBA which was a mess. So I decided to create a hardware RAID inside each host and use free Starwind VSAN https://www.starwindsoftware.com/starwind-virtual-...


6

You really need RDMA-capable 10 GbE for your backbone connectivity. 4x1GbE is simply not enough for Storage Spaces Direct. Get Mellanox ConnectX3 or similar cards, you can get used/refurb cheap from eBay. P.S. S2D doesn't shine on a two-node config...


6

I may try the 10GBe cards. Trying to pinpoint and prove that its networking that is holding me back. I just can't find evidence of it. RDMA-capable 10GbE NICs is kinda a requirement for S2D. Also, just want to add that @BaronSamedi1958 is right about "S2D doesn't shine on a two-node config..." thereby I would recommend taking a look at SDS solutions that ...


6

You have to have supported media types with Storage Spaces Direct which is no-RAID, no-FC and no-iSCSI. Should be SATA, SAS and NVMe. https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-hardware-requirements Drives Use local-attached SATA, SAS, or NVMe drives. You can easily workaround this issue if you say don't ...


6

Unless you're doing a HEAVILY read-oriented system, Storage Spaces Parity mode is less than optimal. I'd strongly suggest using the Mirror mode. Do note that Mirror in Storage Spaces is NOT RAID1. It functions like RAID1E (mostly). It will divide your disks into chunks, then ensure all data exists on 2 disks (for 4 disks or fewer), or 3 disks (for 5 disks or ...


6

Unfortunately, Storage Spaces Direct has hardware limitations which mean that even if you succeed with a workaround for this issue final configuration will not be supported anyway. If Storage Spaces Direct is not mandatory you can use HPE's native hyper-converged solution https://www.hpe.com/emea_europe/en/storage/storevirtual.html that does basically the ...


Only top voted, non community-wiki answers of a minimum length are eligible