Virtual Machine migration and high availability solution

The company has three physical servers, installed windows server 2008 R2, and enabled Hyper-v. Each of the three physical servers has three virtual machines (9 in total ). The current environment does not support high availability of virtual machines. We plan to configure a windows Cluster to support high availability of virtual machines. Note: virtual machines are all fixed-size Disks without SCVMM.

1) Do I no longer need an arbitration disk to configure windows clusters on the three physical servers?

2) What should I do if I want to migrate nine VMS to the cluster to achieve high availability? Export the VM to the cluster disk, delete the original Vm, and then import the VM to the cluster disk? Is SCVMM required?

3) after the cluster is implemented, we need to implement one physical server to manage three VMS. Do you need to allocate nine VMS to three Luns, are different physical servers used to control different Luns?

A: For your question, on 2008 and 2008 R2, the quorum mode is greatly changed compared with the previous 2003. then the arbitration disk is not necessarily necessary. Now we use a voting mechanism. Each node has a vote. You can use fileshare witness or disk witness to vote for arbitration. You can also use only nodes as vote. Specifically, the following 4 modes you see the article from the Active Directory SEO http://gnaw0725.blog.51cto.com/156601/d-3

Node Majority quorum mode Node Majority Arbitration mode

Node and Disk Majority quorum mode

Node and File Share Majority quorum mode Node and File Share Majority Arbitration mode

No Majority: Disk Only quorum mode arbitration Disk mode

Back to your environment, the use of Node Majority quorum mode on the three machines is the Arbitration mode in which nodes are used to vote. For more information about the Arbitration mode, refer to the following TechNet article.

 

 

Appendix B: Additional Information About Quorum Modes

Http://technet.microsoft.com/zh-cn/library/cc770830 (WS.10). aspx

 

 

For the high availability solution of the cluster, you can refer to the following TechNet article to provide the Live migration solution. The procedure is as follows:

 

 

Hyper-V: use real-time migration with cluster shared volumes in Windows Server 2008 R2

Http://technet.microsoft.com/zh-cn/library/dd446679 (WS.10). aspx

 

 

That's normal high availability without using CSV (cluster shared volume), you just need to put the virtual machine's VHD into the cluster shared disk, create a virtual machine by using the VHD on the shared disk in the Hyper-V manager, and then create a service and application-"virtual machine through the cluster manager, enable high availability for virtual machines already created on a shared disk. For detailed steps, see the following article: Active Directory SEO http://gnaw0725.blog.51cto.com/156601/d-3

 

 

Hyper-V: Using Hyper-V and Failover Clustering

Http://technet.microsoft.com/zh-cn/library/cc732181 (WS.10). aspx

 

 

This is not required for your last problem. The virtual machine is a separate cluster resource and can be managed separately.

 

 

Eric Guo

This article is from the "Active Directory SEO" blog