How to build Microsoft Scale-Out File Server without SAS JBODs
•Télécharger en tant que PPTX, PDF•
1 j'aime•2,475 vues
Microsoft Scale-Out File Server is a new efficient storage solution for Hyper-V and SQL. SoFS uses SMB 3.0 to eliminate all the complexity of traditional shared storage and leverages the clustering capabilities to maintain true storage high availability. While most of the vendors show how SoFS is configured with shared JBOD storage, we will show you how to configure it with just local storage and zero additional hardware.
Recommandé
Recommandé
Contenu connexe
Plus de StarWind Software
Plus de StarWind Software (12)
Dernier
Dernier (20)
How to build Microsoft Scale-Out File Server without SAS JBODs
- 1. StarWind Native SAN for Hyper-V 6.0 The Right Tool to Run Hyper-V Creative Services 2014 Global Marketing & Enablement Max Craft How to build Microsoft Scale-out File Server cluster without SAS JBODs Max Kolomyeytsev StarWind Virtual SAN Product Manager
- 2. StarWind At-A-Glance Leading Storage Virtualization and iSCSI SAN Software Ownership: Privately held since 2003 Product: StarWind™ storage virtualization software Users: 30,000+ customers in over 100 countries Headquarters: Burlington, MA, USA R&D office in Europe Support: Worldwide, 24x7x365 support Infrastructure Global Channel: Two-tier indirect sales channel, VARS & System Integrators Global Alliance Partners: Microsoft, VMware, Citrix, HP, IBM, Dell, VEEAM Logistics • You can download this presentation after the webinar • This webinar is being recorded for replay • Watch for other StarWind events and activities • Follow us on Facebook, Spiceworks, and Twitter • Get your free copy of “StarWind Virtual SAN for Microsoft SOFS” whitepaper by Greg Schulz from StorageIO
- 3. About Max Kolomyeytsev StarWind Virtual SAN Product Manager 7+ years of QA and technical support experience @ StarWind Software 10+ of professional IT experience Host of the StarWind Technical Webinar series
- 4. Agenda • The idea of simplifying storage for Hyper-V • SMB 3.0 as Microsoft’s future primary network storage protocol • Scale-Out File Server general overview • SoFS Cluster hardware requirements • Scaling down SoFS cluster hardware requirements • Q&A
- 5. StarWind At-A-Glance Leading Storage Virtualization and iSCSI SAN Software Ownership: Privately held since 2003 Product: StarWind™ storage virtualization software Users: 30,000+ customers in over 100 countries Headquarters: Burlington, MA, USA R&D office in Europe Support: Worldwide, 24x7x365 support Infrastructure Global Channel: Two-tier indirect sales channel, VARS & System Integrators Global Alliance Partners: Microsoft, VMware, Citrix, HP, IBM, Dell, VEEAM Microsoft Software Defined Storage for Hyper-V and SQL Server Product Microsoft iSCSI target Microsoft Scale-out File server Protocol iSCSI SMB 3.0 Usage All applications* (initiator side clustering required) Hyper-V 3.0 and SQL Server Cache Flash SS Flash SS, SMBRX Client Cache Memory Mgr, CSV R/O SMBRX, CSV R/O Snapshots + Offloaded to the application level Load balancing Microsoft MPIO SoFS CSV auto-rebalancing High Availability Active-Passive Active-Active (1-to-1) Maximum servers in the cluster 2 8/16
- 6. StarWind At-A-Glance Leading Storage Virtualization and iSCSI SAN Software Ownership: Privately held since 2003 Product: StarWind™ storage virtualization software Users: 30,000+ customers in over 100 countries Headquarters: Burlington, MA, USA R&D office in Europe Support: Worldwide, 24x7x365 support Infrastructure Global Channel: Two-tier indirect sales channel, VARS & System Integrators Global Alliance Partners: Microsoft, VMware, Citrix, HP, IBM, Dell, VEEAM Scale-Out File Server General overview • Designed for 2 most popular workloads: Hyper-V and SQL • Provides easy to use file-based storage • Scalable by design • Boosts performance with RDMA (SMB Direct) • Supports tiering, flash caching, and offline deduplication (using Storage Spaces and Windows Server functionality)
- 7. SMB 3.0 is a future network storage protocol Microsoft sees SMB 3.0 as a primary future storage protocol, iSCSI is legacy. Reasons: iSCSI spec is complex and controlled by community and SMB is fully maintained by Microsoft CSVFS has issues playing the clustered file system role MSFT sees more flexibility in scaling compute and storage layers independently by using commodity hardware SoFS provides a cost-effective way to scale existing FC and SAS infrastructures
- 8. StarWind At-A-Glance Leading Storage Virtualization and iSCSI SAN Software Ownership: Privately held since 2003 Product: StarWind™ storage virtualization software Users: 30,000+ customers in over 100 countries Headquarters: Burlington, MA, USA R&D office in Europe Support: Worldwide, 24x7x365 support Infrastructure Global Channel: Two-tier indirect sales channel, VARS & System Integrators Global Alliance Partners: Microsoft, VMware, Citrix, HP, IBM, Dell, VEEAM SoFS hardware requirements
- 9. About Bill Kindle IT Administrator with 10+ years experience in SMB settings, primarily focused on Windows Server and virtualization technology support Part time technical consultant Currently works for a firm that develops software for the engineering sector providing support and consulting services to auto, aerospace and defense industry customers.
- 10. SoFS cluster: Traditional (SAS JBOD/FC) VS Hardware-less Shared SAS / FC Hardware-less Storage fabric performance 6 Gb (SAS) – 16 Gb (FC) 1 GbE – 100 GbE Switchless* Additional storage hardware required 2 FC arrays / 3 JBOD arrays none Disk type FC / SAS only SATA / SAS SSD support SAS/FC only SATA/SAS/PCI-E Distributed RAM & Flash cache none both
- 11. StarWind At-A-Glance Leading Storage Virtualization and iSCSI SAN Software Ownership: Privately held since 2003 Product: StarWind™ storage virtualization software Users: 30,000+ customers in over 100 countries Headquarters: Burlington, MA, USA R&D office in Europe Support: Worldwide, 24x7x365 support Infrastructure Global Channel: Two-tier indirect sales channel, VARS & System Integrators Global Alliance Partners: Microsoft, VMware, Citrix, HP, IBM, Dell, VEEAM SoFS cluster: Traditional (SAS JBOD & FC) Vs. hyper-conver
- 12. StarWind At-A-Glance Leading Storage Virtualization and iSCSI SAN Software Ownership: Privately held since 2003 Product: StarWind™ storage virtualization software Users: 30,000+ customers in over 100 countries Headquarters: Burlington, MA, USA R&D office in Europe Support: Worldwide, 24x7x365 support Infrastructure Global Channel: Two-tier indirect sales channel, VARS & System Integrators Global Alliance Partners: Microsoft, VMware, Citrix, HP, IBM, Dell, VEEAM Contact Us! Download StarWind Virtual SAN 30-Day Trial here: www.starwind.com/starwind-virtual-san/ Headquarters: 301 Edgewater Place, Wakefield, MA 01880 USA/Canada: 1-617-449-7717 EMEA and Asia: +44-207-193-67-27 sales@starwindsoftware.com info@starwindsoftware.com
Notes de l'éditeur
- The JBOD configuration in the grey rectangle is the minimum amount of hardware required for Enclosure awareness or simply put “JBOD HA”. The SAS switches can be omitted if one uses 3 HBAs in each SoFS cluster node and direct connects the JBODs to the node.
- In this configuration StarWind mirrors the local storage of the SoFS node and then presents it back to both nodes as a single mirrored disk. The SoFS cluster uses this disk as the CSV for the continuously available SMB 3.0 share. Use of local storage dramatically reduces the hardware footprint of the configuration, while allowing a much more flexible storage device selection. You can now use all possible types of storage including the PCI-E SSD, versus just SAS-based storage devices for the JBOD model. This configuration does also work with JBOD and you can have a mixture of local storage and JBOD storage being presented as SMB 3.0 to the applictation cluster.