Website under construction

Figure 2-58:
An example of a Storage Spaces Shared JBOD deployment 
Storage Spaces Shared JBOD provides many benefits compared to past HA storage systems. However, 
requiring that drive devices are physically connected to every single node limits the type of drive 
devices that you can use and can lead to complex SAS fabric configurations, especially as these 
deployments scale out. 
With Windows Server 2016 Storage Spaces, you now can build HA storage systems using storage 
nodes with only local storage, which is either drive devices that are internal to each storage node or 
drive devices in JBODs, where each JBOD is connected only to a single storage node. This completely 
eliminates the SAS fabric and its complexities, but makes possible the use of drive devices such as 
SATA drive devices, which can further reduce cost or improve performance. Figure 2-59 presents a 
Storage Spaces Direct deployment. 
Figure 2-59:
An example of a Storage Spaces Direct deployment 
It is important to also understand that Storage Spaces Direct is an evolution of Storage Spaces, which 
means that it is an extension of the existing SDS stack for Windows Server. Another important aspect 
is that Storage Spaces Direct uses SMB 3.0 for all intranode (also called east-west) communication, 
and takes advantage of all the powerful features of SMB 3.0, such as SMB Direct (RDMA-enabled 
NICs) for high-bandwidth and low-latency communication, and SMB multichannel for bandwidth 
aggregation and network fault tolerance. 
Implementation details 
Storage Spaces Direct seamlessly integrates with the features you know today that make up the 
Windows Server SDS stack, including SOFS (SMB 3.0), Clustered Shared Volume File System (CSVFS), 
Storage Spaces, and failover clustering. Figure 2-60 illustrates the Storage Spaces Direct stack. 

---

57 
CHAPTER 2 | Software-defined datacenter