The SMB 3.0 protocol was introduced in Windows Server 2012 and in Windows 8.
New SMB features that are introduced in the Windows Server 2012 file server
- SMB Transparent Failover
- SMB Scale Out
- SMB Multichannel
- SMB Direct
- SMB Encryption
- VSS for SMB file shares
- SMB Directory Leasing
- SMB PowerShell
SMB Transparent FailoverBoth the SMB client and SMB server must support SMB 3.0 to take advantage of the SMB Transparent Failover functionality.
SMB 1.0- and SMB 2.x-capable clients will be able to connect to, and access, shares that are configured to use the Continuously Available property. However, SMB 1.0 and SMB 2.x clients will not benefit from the SMB Transparent Failover feature. If the currently accessed cluster node becomes unavailable, or if the administrator makes administrative changes to the clustered file server, the SMB 1.0 or SMB 2.x client will lose the active SMB session and any open handles to the clustered file server. The user or application on the SMB client computer must take corrective action to reestablish connectivity to the clustered file share.
Note SMB Transparent Failover is incompatible with volumes enabled for short file name (8.3 file name) support or with compressed files (such as NTFS-compressed files).
SMB Scale OutBoth the SMB client and SMB server must support SMB 3.0 to take advantage of the SMB Scale Out feature.
SMB 1.0 clients do not contain the required client functionality to access SMB scale-out file shares and will receive an "Access Denied" error message when they try to connect to a scale-out file share.
SMB scale-out file shares are always configured so that the Continuously Available property is set. SMB 2.x clients will be able to connect to SMB scale-out file shares but will not benefit from the SMB Transparent Failover functionality.
Both the SMB client and SMB server must support SMB 3.0 to take advantage of the SMB Multichannel functionality. SMB 1.0 and SMB 2.x clients will use a single SMB connection.