A blog by Jose Barreto, a member of the File Server team at Microsoft.
All messages posted to this blog are provided "AS IS" with no warranties, and confer no rights.
Information on unreleased products are subject to change without notice.
Dates related to unreleased products are estimates and are subject to change without notice.
The content of this site are personal opinions and might not represent the Microsoft Corporation view.
The information contained in this blog represents my view on the issues discussed as of the date of publication.
You should not consider older, out-of-date posts to reflect my current thoughts and opinions.
© Copyright 2004-2012 by Jose Barreto. All rights reserved.
Follow @josebarreto on Twitter for updates on new blog posts.
In this post, I'm providing a reference to the most relevant content related to Windows Server 2012 that is related to the File Server, the SMB 3.0 features and its associated scenarios like Hyper-V over SMB and SQL Server over SMB. It's obviously not a complete reference (there are new blog posts every day), but hopefully this is a useful collection of links for Windows Server 2012 users.
Summaries of SMB 3.0 features in Windows Server 2012:
Articles on File Storage for Application Servers (Hyper-V over SMB, SQL Server over SMB):
Articles on SMB Transparent Failover and SMB Scale-Out:
Articles on SMB Direct (SMB over RDMA) and SMB Multichannel:
Articles on Failover Clustering related to File Server Clusters:
Articles on other SMB 3.0 features and capabilities:
Windows Server File Server Tips and Questions:
Private Cloud Solution Architecture:
TechNet Radio (includes Video) with Bob Hunt and Jose Barreto:
Knowledge Base articles (Support KBs) related to Windows Server 2012 SMB 3.0:
Older posts and videos:
I have a question regarding SMB 3.0 and NIC Teaming in Windows Server 2012. When creating a NIC Team with 2x10GbE you have to choose between the switch modes independent/dependent and address hash/hyper-v port.
Since independent switch mode can send on both nics but only receive on one nic is it true that I won´t get 20GbE both ways with this mode using smb multichannel?
If using LACP and dependent switch mode I would have to connect both ethernet cables to the same 10GbE switch for creating a LACP team, loosing redundancy.
We are about to design an environment with two SMB3 scale out file servers running active/active cluster connected with FC to SAN storage. These file servers will be connected with two 10GbE ports each to two separate HP 10GbE switches giving a total of 40GbE in theory. Hyper-V hosts (DL380G8) will also have an dual port 10GbE adapter in a NIC team for SMB3 traffic and Quad port 1GbE for VM Guest network.
So is LACP for the SMB3 storage the only way to go?
Our final goal is 30 Hyper-V hosts and about 1000 VMs
LACP on the team is certain a good way to go. The only other option is to use the Hyper-V port option, connect the team to the vSwitch and pull 4 ports off the virtual to the parent for SMB3 traffic (you typically only get one, but you can manually add 3 more using PowerShell). This will give SMB Multichannel the opportunity to use the multiple virtual NICs and properly balance the load.
The command for adding additional virtual NICs to the parent is:
Add-VMNetworkAdapter -SwitchName <name> -ManagementOS
You should run this 3 times in order to get 4 total NICs in the parent for SMB traffic. This will give each of them a unique MAC address (as if each were coming from a different VM), and the Hyper-V port option in NIC teaming will properly spread them across the physical NICs in the team.
Try this one out and let us know how it works for you. It should give you both the network fault tolerance and the aggregate bandwidth you are looking for, without requiring LACP or using a single switch.