Hyper-V Storage Technology 2 SMB3.0

1) What is Hyper-V SMB3.0 technology: WindowsServer2012 built-in SMB3.0 file sharing protocol, WindowsServer2012Hyper-V support SMB application shared storage, provides independent and cluster services for all virtual machine files (including virtual machine configurations, VHD files, and snapshots) in the Hyper-V Environment (provides file storage through cluster sharing ), deploy and migrate a shared Hyper-V Environment and solve problems encountered in practical applications. Therefore, to deploy virtual machines in this environment, ensure normal network access between the Hyper-V host and the file server is the key to ensuring shared storage applications of SMB.

2) SMB sharing advantages: a) improves flexibility, Hyper-VSMB shared storage supports real-time migration, and B) Simplifies configuration and management. administrators do not need professional storage device management knowledge, understand the file server; c) Make full use of the converged network; d) Reduce CapEx and OpEx.

3) supported methods:

A) SMB transparent switchover-continuous high availability; transparent failover for applications; Support for planned and unplanned failover; and elasticity for file and directory operations.

B) SMB horizontal scaling-active/active file server cluster; application-oriented storage. Main functions: Activity/activity file sharing, zero-downtime fault tolerance, fast fault recovery, zero-downtime CHKDSK, support for application consistency snapshots, support for RDMA networks, Optimization for server applications, and simplified management; independent File System namespace; cluster shared volume; independent logical File Server (\ FS \ Share); Hyper-V cluster; (supports 64 nodes ).

C) SMB direct connection (SMBoverRDMA)-low latency and low CPU load; advantages: scalability, fast and efficient storage access; high throughput and low latency; Minimum CPU utilization, i/O processing; automatic failover and aggregate bandwidth through SMB multi-channel load balancing. Solution: high-performance application servers, such as remote file access, IIS, Hyper-V and HPC in SQLServer; file servers used for storage communication in clusters and shared volume CSV in clusters ). Hardware requirements: Network Interface (R-NIC) for RDMA functions; three types: iWARP, RoCEandInfiniband.

D) SMB multi-channel-network throughput and Failover; full throughput: aggregation by bandwidth of multiple NICs; use multi-core CPU to provide RSS for receiving ends of multiple NICs ). Automatic failover: SMB multi-channel enables end-to-end fault detection. If yes, you can make full use of the NIC grouping (LBFO) function ). Automatic Configuration: SMB automatically detects and uses multiple paths.

E) SMB encryption-security; end-to-end online SMB data encryption: prevents data eavesdropping/listening attacks on insecure networks. Zero-cost Zeronewdeploymentcosts: No need for IPSec, special hardware devices, and WAN accelerators. It can be configured for individual shares or the entire server. When data passes through untrusted networks, multiple settings can be made: application load passes through insecure networks; WAN connects to branch networks.

F) file sharing VSS supports-backup and recovery; consistent shadow copies are provided for applications stored in WindowsServer2012 file sharing. Backup and recovery solutions. Fully integrated with the VSS Architecture

G) SMBPowerShell-management capability.

4) deployment conditions: a) ActiveDirectory infrastructure; B) Hyper-V hosts must run the WindowsServer2012 operating system; c) Hyper-V hosts have full control permissions on SMB sharing; d) we do not recommend that you deploy the SMB storage server on the Hyper-V host node. Instead, you can build a file server. due to physical restrictions, use two Hyper-V hosts to build SMB-based shared storage virtual machines ).

5) The Hyper-V Server Based on SMB3.0 can be implemented as follows:

A) Support for all Hyper-V virtual machine files; VHD and VHDX files, ISO files, and Hyper-V snapshot files.

B) Host-Based backup: Hyper-VVSS writer supports SMB file sharing, DPM2012SP1, and third-party VSS requests.

C) Real-time migration: Real-time migration of failover clusters without Hyper-V, and real-time migration without sharing through SMB3.0 in the background.

D) online storage migration: fully supports SMB3.0, SMB multi-channel, and SMB direct connection as the Migration source and target.

E) Hyper-V replication: fully supports SMB3.0 as the Migration source and target, and does not need to be copied Based on files or block storage layers.

2: Environment Construction: due to physical environment restrictions, only two physical hosts are used to build a Hyper-VSMB3.0 in non-cluster environment;

Step 1: Install the file server role: Select "add role and function wizard" in "Server Manager" to start the "add role and function wizard" to open the "installation type" dialog box, select "role-based or function-based installation"

Step 2: Select "file storage service"-"file and iSCSI service"-"File Server;

Step 3: After the installation is complete, create the "file service" in the shared folder WindowsServer2012 to provide multiple forms of sharing. However, only "SMB-application sharing" can be used as shared storage for virtual machines, other sharing methods are not supported ):

650) this. width = 650; "width =" 1027 "height =" 705 "title =" SMB1.png "style =" width: 717px; height: 501px; "src =" http://www.bkjia.com/uploads/allimg/131228/0553364020-0.png "alt =" 225611680.png"/>

Step 4: Select "Select Server and shared path". In this tutorial, select "C: \ Shares \ SMB"

Step 5: Configure "Sharing Settings". Keep the default settings for this experiment.

650) this. width = 650; "width =" 772 "height =" 565 "title =" SMB2.png "style =" width: 720px; height: pixel PX; "src =" http://www.bkjia.com/uploads/allimg/131228/05533A043-1.png "alt =" 225704574.png"/>

Step 6: select Custom permissions in the "specify access control permissions" dialog box

650) this. width = 650; "width =" 1044 "height =" 521 "title =" SMB3.png "style =" width: 721px; height: 384px; "src =" http://www.bkjia.com/uploads/allimg/131228/05533A2F-2.png "alt =" 225729174.png"/>

Step 7: click "add", select "select subject", and set full control permissions.

650) this. width = 650; "width =" 604 "height =" 506 "title =" SMB4.png "style =" width: 608px; height: 478px; "src =" http://www.bkjia.com/uploads/allimg/131228/0553363218-3.png "alt =" 225759395.png"/>

Step 8: log on to the DC Machine and create a VM based on "SMB application sharing". When selecting the storage location, select \ hv01 \ Shares \ SMB. The figure shows the path to the created VM.

650) this. width = 650; "title =" SMB5.png "src =" http://www.bkjia.com/uploads/allimg/131228/05533C527-4.png "alt =" 225825338.png"/>

The next chapter describes the High Availability Technology of Hyper-V.

This article is from the Eric1990 blog, please be sure to keep this source http://eric1990.blog.51cto.com/2298455/1297256