Windows Server _hyper-v Hyper-V cluster graphics and text tutorial

Experimental environment:

4 Servers for Windows Server Datacenter operating system

The SRV2012 server installs the iSCSI target server role and configures 2 virtual disks to be shared with two clustered servers.

The cluster server installs the Hyper-V role and cluster features.

Operation Steps:

1. System Cluster Configuration

For specific steps please refer to: http://bbs.winos.cn/thread-132599-1-1.html

This test was followed by the last system cluster environment.

2. Configure Hyper-V high available virtual machine

2.1 Virtual machines created in Cluster Administrator

The Hyper-V role was installed the last time the system cluster was configured, so after the system cluster is configured, the Hyper-V high Availability environment is deployed, and then only the virtual machine is configured.

A Create Virtual machine

Open Cluster Administrator, click Role, click Virtual Machine-New virtual machine

Select the cluster node to host the resource required for the virtual machine.

Enter Virtual machine configuration Wizard

Specify the virtual machine name and storage location

Specify Memory size

Select Virtual Machine network card

Specify the virtual hard disk and store it in the cluster share disk.

Click to complete

High-availability virtual machine creation complete

Then install the Windows Server 2012 operating system on the VM001 virtual machine and configure IP to: 192.168.1.230.

B. Virtual machine High Availability detection

After creating a highly available virtual machine VM001 in Cluster Administrator, the virtual machine now falls on the NODE01 node.

The NODE01 node server is shut down and the cluster automatically switches the VM001 virtual machine to NODE02.

Because the test environment uses a machine configuration is not high, slow, plus iSCSI storage and cluster data are the same network card, so lost more packets.

VM001 virtual machine has successfully switched to cluster node NODE02

2.2 High availability for virtual machine configuration created in Hyper-V Manager

After you configure the cluster, virtual machines are typically managed in Cluster Administrator or SCVMM, but if you use Hyper-V Manager to create a virtual machine, even if you put the virtual machine's data files and storage files into the cluster shared storage, the virtual machines are independent and highly available. To achieve high availability of these virtual machines, the configuration steps are as follows:

A Creating a virtual machine in Hyper-V Manager

Open Hyper-V Manager on NODE01 and create a new virtual machine.

Select "Next"

Specify the virtual machine name and storage location and click Next

Specify the memory size and click Next

Specify Virtual Machine network card

Windows Server Hyper-V cluster

2013-01-15 13:44:21 Comment

Specify virtual machine hard disk storage location

Click to complete

Installs the Windows Server 2012 Data Center version of the operating system for the VM01 virtual machine and configures IP to 192.168.1.210.

B Configure high availability for virtual machines

In Cluster Administrator, right-click Roles and click Configure Roles

Click "Next"

Select "Virtual Machine" and click "Next"

Select Virtual Machine VM01

Information confirmation, click "Next"

Enable completion

The virtual machine VM01 can be seen in the role of the Cluster Administrator after the configuration is complete and is not displayed in the role when high availability is not enabled.

C. Virtual Machine High Availability test

This test did not simulate cluster node server failure, and directly to the virtual machine to perform migration operations.

In Cluster Administrator, right-click the VM01 virtual machine, click Move-Live migration-best node

In migration

Migration complete

A ping test was opened and 3 packets were lost.

Digression: In 2008 R2 Hyper-V in the forced shutdown of the virtual machine button is "Shut down", it is easy to confuse, to 2012 has been translated into a "forced shutdown", good understanding more.

However, in the 2012 cluster, it is so, do not know the official version of the system is not the case.

Test completed!