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
- Hyper-V live migrations: Which settings ensure the best performance?
- SAN? NAS? Public cloud? Let’s pick the secondary storage
- How to remotely enable Remote Desktop on another computer
- How to reset the 120-day RDS grace period on Windows Server 2016 without GUI
- PowerShell commands & scripts do not work. How can I fix it?