Netherlands: Software

Introductie Windows Server 2016

Issue link: http://hub-nl.insight.com/i/692748

Contents of this Issue

Navigation

Page 80 of 173

72 C H A P T E R 3 | Storage Storage Spaces Direct Enterprises and service providers are continually looking for ways to deploy private clouds while reducing storage cost, accelerating initial deployment, and simplifying management and monitoring. Storage Spaces, a software-defined storage (SDS) capability introduced previously in Windows Server 2012 and enhanced in Windows Server 2012 R2, provides cost-effective shared storage solutions that are highly available, scalable, and simple to operate, providing a platform for private clouds or private hosted cloud solutions. Windows Server 2016 Technical Preview builds on the SDS capabilities of the previous versions by introducing Storage Spaces Direct, which makes it possible for you to build highly available storage systems using local storage. This provides increased flexibility because you can use new device types such as SATA or NVME drives for creating pooled storage. Scalability is increased because you can add new server nodes with internal storage on an as-needed basis; you can use more drive devices in a single pool as well, simplifying management. Storage expandability is simplified through the action of automatic storage rebalancing. With all of these enhancements, Storage Spaces Direct provides businesses with greater flexibility for deploying storage in private cloud solutions. To help understand Storage Spaces Direct, let's begin by examining Storage Spaces in Windows Server 2012 R2 HA storage systems. In Windows Server 2012 R2, an HA system using Storage Spaces requires drive devices to be physically connected to all storage nodes. For the drive devices to be physically connected to all storage nodes, they need to reside in an external JBOD chassis, with each storage node having physical connectivity to the external JBOD. Also, because multiple storage nodes will be connecting to each drive, the drive devices need to be serial-attached SCSI (SAS) because the SAS protocol allows for this sharing where drives such as SATA do not allow multi-initiator. Because of these requirements, this deployment is referred to as Storage Spaces Shared JBOD to contrast it with Storage Spaces Direct. Figure 3-8 shows a Storage Spaces Shared JBOD deployment. Figure 3-8: 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 Technical Preview Storage Spaces, you can now 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 3-9 presents a Storage Spaces Direct deployment.

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie Windows Server 2016