Updated Links on Windows Server 2012 File Server and SMB 3.0

avatar of josebarretoJoseBarreto20

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:

Step-by-step instructions:

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:

Case Studies

Knowledge Base articles (Support KBs) related to Windows Server 2012 SMB 3.0:

Protocol Documentation:

Older posts and videos:

-------

Change tracking:

  • 04/24/2012: Original post
  • 05/01/2012: Update: Added links to two SNW Spring 2012 presentation
  • 05/03/2012: Update: Added links to protocol documentation, blog post on SMB Encryption and private could blog post 
  • 05/18/2012: Update: Added links to SDC presentations, plus blogs on basics of SMB PowerShell and SMB PowerShell
  • 06/13/2012: Update: Added 3 new blog post, one new KB article, one new video link
  • 08/02/2012: Update: Additional blog posts and links to TechEd recordings
  • 08/26/2012: Update: Two additional blog posts
  • 11/27/2012: Update: Added 10 file server tips, SNW Fall 2012 presentations, TechNet Radio links. Moved older posts down.
  • 01/03/2013: Update: Added 1 TechNet Radio link, 1 white paper, 1 KB article. Added numbers of KB articles next to links.
  • 02/02/2013: Update: Added links to a few new blog posts and white papers
  • 03/11/2013: Update: Added links to 2 new TechNet Radio shows, 5 new blog posts, separate group for step-by-steps
  • 04/11/2013: Update: Added 1 link to TechNet Radio show, 5 new blog posts, 3 new KB articles
  • 05/05/2013: Update: Added 1 MMS link, 1 new TechNet article, 1 new tip, new section on case studies with 3 entries
Comments (20)

  1. Anonymous says:
    July 25, 2017 at 2:50 am
    1. Introduction

      Windows Server 2012 includes a new feature called SMB Multichannel, part of the

    Reply
  2. JoseBarreto says:
    July 25, 2017 at 2:50 am

    @Aleksandar

    The link was fixed. Thanks for catching that.

    Reply
  3. Anonymous says:
    July 25, 2017 at 2:50 am

    This is a very comprehensive and superb post with all the necessary links to knowing/understanding SMB 3.0. I have a question on NIC Teaming which I hope I can get some answers on. In one of the video presentation (link in the blog post) there is mention of a NIC team that can be set as Active/Standby. When the Active is down, the standby kicks in and becomes Active. And when the original Active is recovered, the team automatically fails back to the original Active. Can this automatic fallback be prevented? i.e.: I do not want the team to switch the Active back to the original NIC, but keep the Standby running as Active, until such time when the Standby experiences a problem. (something similar to using the Smart Load Balancing/Auto-Failback Disable (SLB/AfD), when teaming NICs using the BroadCOM suite on Windows 2008 R2).

    Reply
  4. Anonymous says:
    July 25, 2017 at 2:50 am

    I apologize if this isn't the right place for posting such questions: I have a small business network and a client app written in .NET. Multiple users use this app to insert and query in rapid succession into and from an access database which is located on a network drive; a connection is opened once before the inserts and querying begins. The app then uses the oledbdataadapter.fill and .update methods with datatable, and I'm compiling with VS 2010 Express with updated references afaik.

    The client works well with a single user whether he uses SMB 1.0 or 2.0, and it works fine with multiple users if they are all configured to use SMB 1.0. However, in a mixed environment of SMB 1.0 and 2.0 (which so far is unavoidable since we have XP machines we sometimes use) we often see the following exception thrown by oledbdataadapter:

    "Your network access was interrupted. To continue, close the database, and then open it again."

    Once in a while, the dataadapter will also just return an empty table. Our server is Windows Server 2010 and is using SMB 2.1. Any help is appreciated.

    Reply
  5. Jeffrey S. Patton says:
    July 25, 2017 at 2:50 am

    This is awesome Jose! Thanks!

    Reply
  6. JoseBarreto says:
    July 25, 2017 at 2:50 am

    @sunilnair4u

    I talked to the PM working with NIC teaming about your question.

    Unfortunately, there is no way to prevent failback in the NIC teaming situation you mentioned.

    Reply
  7. Anonymous says:
    July 25, 2017 at 2:50 am

    Hi

    I have a team and a hyper-v virtual switch (hyper-v port / lacp) with 2 Server Intel i350-T2 (DualPort) Cards. RSS in the Windows Builtin-Driver is enabled on both Ports. The maximum Number of RSS Queues is set to 4.

    The Switch is a Zyxel 1910-24 with LACP.

    Effektiv Speed by copying Files from Host A to Host B is only 1 Gb / max.

    Get-SmbServerNetworkInterface says that RSS Capable = false (IP of the Host)

    also

    Get-SmbClientNetworkInterface says that RSS Capable = false (vEthernet)

    I had the same Problem with other Nics, so i ordered this new Intel Interfaces.

    Any idea whats going wrong here? How checks Windows, if a card is capable or not?

    Tx a lot.

    Reply
  8. JoseBarreto says:
    July 25, 2017 at 2:50 am

    @Dustyny1 - Have you baselined the storage subsystem on the server side? The most common bottleneck I have seen is the backend storage subsystem. If the storage does not perform locally, SMB 3.0 will not go beyond that.

    Reply
  9. Marc Lognoul says:
    July 25, 2017 at 2:50 am

    Thanks for the update. I wish you'd mirror this post to TechNet Wiki

    Reply
  10. JoseBarreto says:
    July 25, 2017 at 2:50 am

    @Fabrizio

    You should be able to use NIC Teaming and SMB Multichannel and achieve the aggregated throughput of the team if you're using LACP and the right type of teaming (Address Hash). You might want to try increasing the number of SMB connections per RSS NIC (also applies to team) by using:

    Set-SmbClientConfiguration -ConnectionCountPerRssNetworkInterface 8

    Reply
  11. Aleksandar Nikolić says:
    July 25, 2017 at 2:50 am

    •Windows Server 2012 Beta - Test cases for Hyper-V over SMB (includes PowerShell examples) link doesn't work.

    Reply
  12. JoseBarreto says:
    July 25, 2017 at 2:50 am

    @Alexandere

    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.

    Reply
  13. Anonymous says:
    July 25, 2017 at 2:50 am

    Hi,

    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

    Thanks

    Alexander

    Reply
  14. JoseBarreto says:
    July 25, 2017 at 2:50 am

    @RandallT

    To be clear, if your server is using SMB 2.1 (Windows Server 2008 R2) but your client is using SMB 1.0 (Windows XP), the negotiated session will be SMB 1.0.

    Having said that, you seem to be having a specific issue with shared access to the a single file. SMB does allow for this, but the application should not open the files exclusively and locks are sometimes recommended to avoid common concurrent access issues. This is not diferent from having two instances of an application in the same computer accessing a file in a local disk.

    I haven't used Access in a long while and I'm not sure what the expected behavior is. I would suggest you post the question to an access blogger or forum.

    Reply
  15. James van den Berg says:
    July 25, 2017 at 2:50 am

    Hi Jose,

    Great link collection about Windows Server 2012 and SMB 3.0 !

    Thanks a lot.

    Cheers, James van den Berg

    Reply
  16. Anonymous says:
    July 25, 2017 at 2:50 am

    Any chance we'll see some articles on what to expect for performance, how to troubleshoot, and optimize?

    I'm running in to a performance problem when using Hyper-V over SMB 3 and I'm not sure how to go about troubleshooting it. I'm using Mallanox connectx 2 Infiniband adapters and I can pass data at 3GBs so I have really fast interlinks but from my tests, SMB great for large sequential transfers (3GBs) where I max out the PCIe bus (8x) but on smaller transfers 4-512k performance and iOPs is really heavily impacted and writes speed falls off a cliff (20-40MBs).

    Reply
  17. Joseph Sonnier says:
    January 27, 2013 at 5:35 pm

    I am interested in the client side of the equation also.  In particular, I am looking for more information on the transparent caching (Windows 7/8) features and how they interact on the client side with the new SMB 3.0 services.  

    Can you point me in the right direction to getting more internal details - possibly a contact who might be familiar with the internal details and performance of the various interactions?

    Reply
  18. Fabrizio says:
    February 12, 2013 at 10:46 am

    Hello!

    I'm having strange behaviours. I've done a NIC teaming with LACP to provide channel aggregation to multiple protocols, I've disabled RSS because not all NICs are RSS capable, but file transfers between 2 servers stay at 2gb/s even if I have teamed 4 nics.

    is this expected?

    Reply
  19. Anonymous says:
    March 30, 2014 at 10:09 pm

    In this post, I'm providing a reference to the most relevant content related to Windows Server 2012

    Reply
  20. Anonymous says:
    July 7, 2014 at 4:23 pm

    In this post, I'm providing a reference to the most relevant content related to Windows Server 2012

    Reply
Skip to main content