Jose Barreto's Blog - All Comments

re: File Server Tip: How to rebalance a Scale-Out File Server using a little PowerShell

Jose Barreto - MSFT — Wed, 17 Apr 2013 21:22:11 GMT

@Harald

You're correct. You need SMB 3.0 (Windows 8 or Windows Server 2012 on both sides). There are just too many changes in the new SMB version to make a backport viable.

However, the Scale-Out File Server scenario is focused mostly on servers, so maybe for a new Hyper-V over SMB or SQL Server over SMB scenario the Windows Server 2012 deployment could more easily be made part of the plan.

re: File Server Tip: How to rebalance a Scale-Out File Server using a little PowerShell

Harald — Wed, 17 Apr 2013 21:12:33 GMT

Sounds great. My main problem is to roll out windows 8 to use the new client SMB features...

re: Iron Networks shows a complete private cloud pod at MMS 2013 with Windows Server 2012 (Storage Spaces, SMB3, Hyper-V) and System Center 2012 SP1

Harald — Wed, 17 Apr 2013 21:03:30 GMT

Wow impressive! I will adapt some ideas for our infrastructure. Different storage tiers e.g!

re: MMS 2013 Demo: Hyper-V over SMB at high throughput with SMB Direct and SMB Multichannel

Sass — Wed, 10 Apr 2013 17:59:39 GMT

Jose;

I know it is completely irrelevant to this post, but I was wondering whether you know what happened to the Routing and Remote Access Blog. it is not updated anymore despite the fact that there were some awesome pieces of information posted there which proves that it was a useful blog.

I even tried the Email Author link on it but it got bounced back by Microsoft mailer so it seems that the rrasblog at microsoft dot com email is no longer in service either.

the blog address:

blogs.technet.com/.../rrasblog

re: Slides for the Instructor-Led Lab on Windows Server 2012 Storage from MMS 2013

Faisal Masood (EPMAdmin.com) — Wed, 10 Apr 2013 03:56:22 GMT

Thanks for the info.

Faisal Masood

http://www.EPMAdmin.com

http://www.softvative.com

re: File Server Tip: How to rebalance a Scale-Out File Server using a little PowerShell

Valentin Lecerf — Thu, 04 Apr 2013 06:43:03 GMT

Very good post!

re: SQLIO, PowerShell and storage performance: measuring IOPs, throughput and latency for both local disks and SMB file shares

Andre Muraro — Mon, 01 Apr 2013 22:57:34 GMT

I've used this in my DEMO tests and it worked very well

Thanks for sharing this, awesome work!

re: Q & A: I only have two NICs on my Hyper-V host. Should I team them or not?

Denis Dyagilev — Sun, 31 Mar 2013 15:48:04 GMT

Great article, thanks, Jose.

re: SQLIO, PowerShell and storage performance: measuring IOPs, throughput and latency for both local disks and SMB file shares

tonyr — Thu, 28 Mar 2013 16:09:56 GMT

awesome very good work.

re: Updated Links on Windows Server 2012 File Server and SMB 3.0

Jose Barreto - MSFT — Wed, 13 Mar 2013 15:15:34 GMT

@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.