September, 20 1pm PT
Live StarWind presentation
Meet industry-first
software-defined NVMe
over Fabrics
Target and Initiator
for Microsoft Hyper-V and
VMware vSphere
Posted by Ivan Talaichuk on December 6, 2017
High-performing and highly available Scale-Out File Server with SMB3

There’s, probably, no IT administrator who hasn’t heard of SMB3 (Server Message Block). is an application-layer network protocol, developed by Microsoft mostly to provide shared access to the files, and allowing communication between nodes. SMB has been designed as a tool for the creation of a DOS-based network file system, but Microsoft took the initiative and renamed SMB into CIFS later on (Common Internet File System) and continued further developing it. The second version – SMB 2.0, has been introduced in Windows Vista with a wide range of new features, thus it became clear that Microsoft was working hard to improve this protocol.

Learn More

Posted by Didier Van Hoye on November 21, 2017
Take a look at Storage QoS Policies in Windows Server 2016

In Windows Server 2016 Microsoft introduced storage Quality of Service (QoS) policies.  Previously in Windows Server 2012 R2, we could set minimum and maximum IOPS individually virtual hard disk but this was limited even if you could automate it with PowerShell. The maximum was enforced but the minimum not. That only logged a warning if it could be delivered and it took automation that went beyond what was practical for many administrators when it needed to be done at scale. While it was helpful and I used it in certain scenarios it needed to mature to deliver real value and offer storage QoS in environments where cost-effective, highly available storage was used that often doesn’t include native QoS capabilities for use with Hyper-V.

Learn More

Posted by Anton Kolomyeytsev on October 17, 2014
Storage Replica: “Shared Nothing” Scale-Out File Server

This post is about Microsoft Storage Replica – a disaster recovery tool, introduced by Microsoft in Windows Server 2016. It is a part of series about this technology, which is all featured on this blog. Basically, the post is a practical guide for building a “Shared Nothing” Scale-Out File Server, prepared by StarWind engineers after they did it themselves. The “Shared Nothing” is an architecture, which implies that each node is self-sufficient and completely independent, which makes the system more reliable. It got its name because the nodes don’t have a shared storage at all, moving closer to eliminating the single point of failure. The architecture is almost infinitely scalable, becoming popular with use cases where unpredictable and explosive growth is typical.

Storage replication
Learn More