How does SMB work? And what's new in SMB 3.0?
Even the simplest network uses a variety of protocols and standards, allowing servers and other network devices to exchange data and run client-server applications. But it's not enough for modern network file-sharing protocols to simply move data from one point to another -- the protocol must scale, aggregate available bandwidth, move data directly to or from memory, support encryption and perform other tasks critical to everyday enterprise uses. Windows Server relies on the server message block protocol for file sharing across the enterprise data center.
The server message block (SMB) protocol enables workloads to exchange files and initiate services from local or remote computers across a TCP/IP network.
The most current version of SMB is 3.02, appearing in Windows 8.1 and Windows Server 2012 R2. Since SMB is primarily intended to exchange files, it is best used for storage-related tasks, and SMB 3.0 (in Windows Server 2012 and later) supports storage-intensive applications.
Although client-side applications have long used SMB to exchange files with local servers, SMB 3.0 adds better support for remote data exchange across WAN links; this reduces latencies for remote offices accessing centralized servers, while adding security to help prevent data theft. Microsoft Hyper-V in Windows Server 2012 (and later) also supports SMB 3.0, allowing the hypervisor to exchange .VHD files and snapshot files with both standalone (local) and shared storage resources. SMB 3.0 also supports Live Migration, offering the ability to improve the performance of enterprise virtualization, especially on highly consolidated systems with heavy storage activity.
In addition, SMB 3.0 is tailored to high-end enterprise applications. For example, it will interoperate with Microsoft's SQL Server 2008 R2 to store database files on SMB file shares while improving performance and reducing latency -- this can provide significant improvements for large database files.
Dig Deeper on Windows File Management
Related Q&A from Stephen J. Bigelow
Not all hypervisors and OSes can play nice with others. The best method for avoiding complications down the road is to thoroughly test your nested ...continue reading
Theoretically, there is no limit on how 'deep' a nested VM can go. The best way to avoid any confusion is to appropriately label hypervisor nesting ...continue reading
Interested in giving nested virtualization a try in your data center? There are a few software and hardware requirements you'll have to meet first.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.