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 R2 that is related to the File Server, the SMB 3.02 features and its associated scenarios like Hyper-V over SMB and SQL Server over SMB. This is what some like to call a "Survival Guide" for SMB 3.02. t's obviously not a complete reference (there are always new blogs and articles being posted), but hopefully this is a useful collection of links for Windows Server 2012 R2 users.
This post covers only articles that are specific to Windows Server 2012 R2. However, note that there’s also a Windows Server 2012 version of this post. Most concepts, step-by-steps and tools listed there also apply to Windows Server 2012 R2.
TechNet articles on Windows Server 2012 R2 File Server and SMB 3.02 (and related topics)
Blog posts on Windows Server 2012 R2 File Server and SMB 3.02 (and related topics)
Step-by-step instructions for Windows Server 2012 R2 File Server and SMB 3.02 (and related topics)
TechEd 2013 presentations (with video recording) on Windows Server 2012 R2 File Server and SMB 3.0 (and related topics)
Demos, Interviews and other video recordings
Windows Server 2012 R2 download links
Windows Server 2012 R2 – RDMA NIC Drivers
Blog posts by Microsoft MVPs on Windows Server 2012 R2 File Server and SMB 3.02 (and related topics)
Posts on Windows Server 2012 and SMB 3.0 that still apply to Windows Server 2012 R2 and SMB 3.02:
Other relevant links related to Windows Server 2012 R2 SMB features
Knowledge Base - KB Articles
<p>Dear Jose Barreto,</p>
<p>Many links in under “Updated Links on Windows Server 2012 R2 File Server and SMB 3.0” especially “Blog posts by Microsoft MVPs on Windows Server 2012 R2 File Server and SMB 3.0 (and related topics)” point to the same demo: “SMB performance demo from TechEd.wmv”.</p>
<p>That is, I think, an error.</p>
<p>I believe those links are fixed, now, JanV.</p>
<p>I wonder if there is any guidelines to size properly (ram, processing) a SMB3 server to use with VDI or other virtualized loads</p>
<p>Dear Jose Barreto,</p>
<p>Thank you for repairing the links.</p>
<p>It needs to be mentioned that your blog is very good. Outstanding.</p>
<p>You are probably aware of that. A tremendous amount of energy and time is (was) needed to make the blog as it is now. Keeping it up-to-date is probably also very time-consuming. Thank you for it.</p>
<p>Another way of looking to your blog is from a client perspective or, alternatively from the perspective of Microsoft willing to sell and promote its product.</p>
<p>We need the info; Microsoft wants to promote its product. Your blog is a very nice way of satisfying the client.</p>
<p>Unfortunately, few Microsoft-departments act as you do.</p>
<p>To be honest, I am quite disappointed about e.g. the team that made (and makes) Storage Spaces.</p>
<p>I cannot find ONE serious whitepaper or blog (or whatever) that clearly explains how to properly setup Spaces (alternatively, I could not find such a story).</p>
<p>That is very bad, because it is the basis of what we want to establish (SMB, Clusters, all is related to Storage Spaces). </p>
<p>Would it be possible to wake up the SS team? Alternatively, could you make a systematic explanation how to enroll SS properly?</p>
<p>This becomes increasingly important when looking at configurations where SSD and HDD’s are mixed for the various ways of caching (in R2). With SS, we have nice new opportunities, but no details / explanations. Bad.</p>
<p>In addition, the Deduplication team could become more active.</p>
<p>Deduplicated Hyper-V guests generate very nice new possibilities. Also no details / whitepapers or whatever.</p>
<p>A more general question (you do not need to answer): why does Microsoft for some products has excellent blogs / whitepapers like yours? Alternatively, why are teams sometimes acting as if they develop new products exclusively for themselves? </p>
<p>I very much like Didier Van Hoye’s blog <a rel="nofollow" target="_new" href="http://workinghardinit.wordpress.com/2013/06/21/teched-2013-revelations-for-storage-vendors-as-the-future-of-storage-lies-with-windows-2012-r2/">workinghardinit.wordpress.com/.../teched-2013-revelations-for-storage-vendors-as-the-future-of-storage-lies-with-windows-2012-r2</a> </p>
<p>We (including Microsoft) have to work hard to make this work.</p>
<p>Without proper promotion, proper explanation, proper hardware etc., this nice product will not turn out to be the success it deserves.</p>
<p>With a SOFS cluster, is it possible to force one (or some) node(s) to be favoured, such that clients will prefer to connect to it unless it isn't available ?</p>
<p>Is SOFS on top of SAN storage a supported configuration ?</p>
<p>The whole notion of the Scale-Out File Server is that we spread the clients across nodes. The only exception is when a specific node has a better path (CSV coordination node on a Mirrored Storage Space) so in that case we favor that specific node.</p>
<p>SOFS with a SAN back-end is definitely supported.</p>
<p>The scenario I am thinking of is a SOFS across datacentres, where we want the servers connecting to the SOFS storage within each datacentre to prefer connecting to the "local" nodes, but still be able to leverage the "remote" nodes if the local ones go down (/need maintenance, etc).</p>
<p>Is this possible ?</p>
<p>Assume there is adequate bandwidth between sites (10s of Gb) and the underlying storage system can maintain coherency (eg: VPLEX).</p>
<p>Any info on where Storage Server 2012 R2 fits into the file server picture this time around?</p>
<p>Yeah, I know it's primarily an OEM build, but I have been using it for a now outdated Dell PowerEdge SMB NAS (2003 R2 no-less) and on a couple HP MicroServer builds at home, and as a file server option is has worked nicely.</p>
<p>Previously it was the easy way to get iSCSI support, but that's kinda baked into all Windows Server SKUs now.</p>
<p>But I can't really find any updated info on Storage Server - is there any point in using it now from a technical perspective? (I know there might be something in the licensing department, but that's a secondary concern.)</p>
<p>@Andreas Helland </p>
<p>Windows Storage Server 2012 R2 shares the same functionality and capabilities of Windows Server 2012 R2. The difference now is just licensing. You can find details at <a rel="nofollow" target="_new" href="http://blogs.technet.com/b/storageserver">blogs.technet.com/.../storageserver</a> </p>
<p>The typical Hyper-V over SMB solution is not a "stretch" cluster, but it contained to a single data center. The solution I usually offer for cross-site replication is Hyper-V Replica. </p>
<p>Having said that, you could make it happen with shared storage that is replicated across sites. But that requires 3rd party solutions for block replication.</p>
<p>Our hypervisor platform is VMware, and this is unlikely to change.</p>
<p>Hyper-V replica would be unsuitable as it cannot replicate synchronously.</p>
<p>We have a suitable storage system - VPLEX. What I'm interested in is whether it's possible to give SOFS nodes a preference based on proximity, to prevent SOFS clients in one site accessing SOFS nodes in the other, unless the local ones are unavailable.</p>
<p>I'm from EMC and met you in person this year after many years of reading your blog. We talked about the future potential of SMB3.0 for our customers. I was wondering if you wouldn't mind checking out my latest blog post to tell me what you think: <a rel="nofollow" target="_new" href="http://powerwindows.wordpress.com/2013/11/04/building-a-microsoft-azure-private-cloud-powered-by-vnx-storage/">powerwindows.wordpress.com/.../building-a-microsoft-azure-private-cloud-powered-by-vnx-storage</a></p>
<p>It's all about leveraging the great combination of technologies that Microsoft has provided, supported by EMC infrastructure. </p>
<p>Thanks a lot. <unrelated link removed></p>
<p>Thanks a lot for this amazing Blog. There are so many interesting things to read ...</p>
<p>Your post about the 8.3 name issue is very extensive, but i'm missing a statement to 8dot3 on the System Volume. Why is it there already enabled, also on current Windows Server 2012 or R2?! Is there any reason, why i shouldn't change that?</p>
<p>The main issue I heard of with 8.3 on system volumes relates to installers (and uninstallers). Some of them still use the short name path and removing those can cause uninstallers to fail. The removal tool actually tests for references in the registry to these short names and warns before removing. For data disks, there's much less concern.</p>