SMB 3.0, with its long list of enhancements, has become increasingly viable in the building of public or private clouds by deploying Hyper-V over SMB. The solution stack in general involves three layers. The top layer consists of Hyper-V hosts and VMs. The middle layer consists of the file servers for managing the SMB file shares. And the bottom layer is the storage.
Clustered Data ONTAP 8.2 (or later) has built in the support of SMB 3.0 for Hyper-V 2012, with FlexVol volumes. On a Storage Virtual Machine (SVM, formally known as Vserver), you can add the CIFS server role. The CIFS server behaves similar to a Windows file server: it can join a Windows Active Directory domain and manage SMB file shares. This means that if you choose to deploy Hyper-V over SMB on NetApp FAS storage systems running Clustered Data ONTAP (cDOT), you can simplify the solution by collapsing the 3-layer stack into two layers. The middle layer (file servers) is consolidated into the cDOT storage layer.
In addition to simplifying the solution, there are many other benefits when deploying Hyper-V over SMB on NetApp. Below are a few highlights.
Of course, scale-out is another often-mentioned capability of Clustered Data ONTAP, which allows you to grow your Hyper-V clouds non-disruptively.
Thanks for reading.