So, we all know about Microsoft’s Storage Spaces Direct (S2D to put it simple) by now. It’s the feature introduced in Microsoft Server 2016 (Datacenter Edition) that pools together server’s storage allowing to build…that’s right: highly available and easily scalable software-defined storage systems. In this article, I’m gonna talk about not as much about its fault-tolerance characteristics themselves, but some hands-on experience, namely: how to replace a failed disk.
Subscribe to my posts
- Several tips and hints to full-throttle your Hyper-V performance
- Hot adding/removing memory in Hyper-V 2016: a closer look at the feature
- Performance or protection? How Microsoft patches against Meltdown and Spectre influence CPU, RAM and Disks performance
- How to save disk space in Clustered File Servers on Windows Server 2016 using Data Deduplication feature
- The idea Behind Node Fairness in Hyper-V: How it works and why you need it?