Hyper-V 3.0 Server Virtualization: creating a solid cloud

I have been busy recently, so my blog updates seem very slow. I am very grateful to you for your support. Today's content has little to do with Lync, mainly to share with you something about Hyper-V. I believe everyone is familiar with Hyper-V. It seems that there is not much to say. However, I believe that Hyper-V 3.0 still has a lot of changes worth our hearts.

Next we will look at a standard Hyper-V Architecture Based on Windows Server 2012. This architecture is very understandable. Two Hyper-V 3.0 hosts are added with a switch and a shared storage server SMB3.0. All architectures and systems are independently completed on Windows Server 2012.

650) this. width = 650; "height =" 484 "title =" clip_image001 "style =" margin: 0px; border: 0px currentcolor; background-image: none; padding-top: 0px; padding-right: 0px; padding-left: 0px; "alt =" clip_image001 "src =" http://www.bkjia.com/uploads/allimg/131228/01052C1O-0.jpg "border =" 0 "/>

The biggest change is the shared storage Server based on SMB 3.0, which is a new feature provided in Windows Server 2012. That is to say, we can directly deploy a Server with High Disk performance, install the Windows Server 2012 operating system, and deploy it as an SMB 3.0 Shared File Server, which can be used as shared storage by multiple Hyper-V hosts. It can be used to store virtual machine configuration files, disk files, and smart paging files unique to Hyper-V 3.0, even snapshot files and snapshot configurations can be stored in the file server based on the SMB 3.0 protocol. The advantage is that the VM will not be inaccessible due to the downtime and planned downtime maintenance of the Hyper-V host, and storage can be shared with multiple Hyper-V hosts, this allows you to quickly complete non-stop migration and Vm replication.

In addition, Hyper-V can also achieve real-time migration without shared storage, and provide real-time migration of virtual machines between multiple Hyper-V servers over the network, the advantage of this migration method is that the virtual machine does not need to be shut down, and the virtual machine does not have any changes or perception. The disadvantage is that the Migration takes a long time, if there are many data files on the Virtual Machine disk, it takes a longer time.

650) this. width = 650; "height =" 409 "title =" clip_image002 "style =" margin: 0px; border: 0px currentcolor; background-image: none; padding-top: 0px; padding-right: 0px; padding-left: 0px; "alt =" clip_image002 "src =" http://www.bkjia.com/uploads/allimg/131228/01052C0U-1.jpg "border =" 0 "/>

After reading the standard Hyper-V 3.0 architecture, let's take a look at the Hyper-V 3.0 server virtualization architecture with some high availability features. We can intuitively see from the architecture diagram that the current Windows Server and Hyper-V both have complete high availability features, including the Hyper-V host, storage, and virtual machine layer.

650) this. width = 650; "height =" 484 "title =" clip_image003 "style =" margin: 0px; border: 0px currentcolor; background-image: none; padding-top: 0px; padding-right: 0px; padding-left: 0px; "alt =" clip_image003 "src =" http://www.bkjia.com/uploads/allimg/131228/0105264342-2.jpg "border =" 0 "/>

We can see that the Hyper-V server virtualization architecture diagram is already similar to the standard server virtualization architecture, with the help of Microsoft cluster service, it ensures high availability of virtual machines on Hyper-V hosts and implements fast failover through the underlying SMB 3.0 Shared storage server. But at this moment, we still find that this architecture diagram has limitations, that is, our shared storage still cannot meet our requirements. These restrictions may be performance or availability.

Because we only have one shared storage server based on SMB 3.0 in this topology, although we can create a disk-based storage pool on one storage server. The image, parallel, and redundancy modes are implemented on Windows Server, in other words, we can create multiple single SATA, SAS, SSD, and other types of disks in Windows Server as virtual disk volumes with RAID 0, RAID 1, and RAID 5 arrays, so that our storage has a certain high availability.

Of course, this high availability and performance cannot be guaranteed through a single SMB 3.0 Shared storage server, excluding the possibility of storage pool data errors caused by disk damage, there may also be faults in the shared storage server of SMB 3.0, such as system damage, power failure, and downtime maintenance. One shared storage server of SMB 3.0 cannot cope with these problems.

Therefore, in Windows Server 2012, Microsoft supports clustering SMB 3.0 Shared storage servers to provide cluster shared volumes and advanced features such as traffic redirection and multi-link. In addition, the shared storage server of SMB 3.0 supports the reference of Fiber Channel storage to simplify storage deployment, configuration, and maintenance.

650) this. width = 650; "height =" 484 "title =" clip_image004 "style =" margin: 0px; border: 0px currentcolor; background-image: none; padding-top: 0px; padding-right: 0px; padding-left: 0px; "alt =" clip_image004 "src =" http://www.bkjia.com/uploads/allimg/131228/01052640O-3.jpg "border =" 0 "/>

Finally, we will introduce a complete and high-availability Hyper-V 3.0 server virtualization cluster topology, including a Hyper-V virtualization host server cluster and an SMB 3.0 Shared storage server cluster, of course, after SMB shared storage, you can also reference FCSAN, iSCSI SAN, storage pool, and RAID Controller storage with clusters.

650) this. width = 650; "height =" 484 "title =" clip_image005 "style =" margin: 0px; border: 0px currentcolor; background-image: none; padding-top: 0px; padding-right: 0px; padding-left: 0px; "alt =" clip_image005 "src =" http://www.bkjia.com/uploads/allimg/131228/01052A1T-4.jpg "border =" 0 "/>

In fact, what I'm most interested in here is the connection from SMB CSV to Hyper-V host. If we only use 10-Gigabit optical handed in, the bandwidth may still be limited, after all, the bandwidth from each server to optical traffic is very limited. However, I was relieved by the powerful network aggregation function of Windows Server 2012. With the network gathering function, I can easily aggregate multiple network ports on the Server, this doubles the bandwidth from the server to the optical host.

In Windows Server 2012, the network aggregation function is very shy and hidden in the Server Manager. The official name is NIC combination.

650) this. width = 650; "height =" 339 "title =" clip_image006 "style =" border: 0px currentcolor; background-image: none; padding-top: 0px; padding-right: 0px; padding-left: 0px; "alt =" clip_image006 "src =" http://www.bkjia.com/uploads/allimg/131228/01052A363-5.png "border =" 0 "/>

In the NIC combination dialog box, we can easily group multiple network ports for network aggregation and increase server bandwidth.

Hyper-V Server virtualization is introduced here first. In general, Hyper-V of Windows Server 2012 is very powerful, it is also fulfilling what Microsoft said. This is an operating system optimized for the cloud. In fact, here we can find that Hyper-V is just a platform, on this platform, there are also System Center components to optimize our cloud, so as to implement a truly locally available and reliable private cloud.

This article is from the Reinember blog, please be sure to keep this source http://reinember.blog.51cto.com/2919431/1241044