WIN2012R2 Hyper-V 17 configuration High availability of Hyper-V clusters (top)

In the previous chapters we have done some processing for the regular failed server, that is, to save the copy, so what if we need to achieve high availability? That is, when the server is running low performance or unconventional downtime, it can seamlessly and automatically migrate the corresponding virtual server in real time to ensure uninterrupted 24 hours of business. That's what we're focusing on today. Hyper-V server cluster high availability configuration.

First, the corresponding test network topology diagram is provided to ensure the smooth progress of the experiment.

A. Failover cluster installation

1. First we install the Failover Clustering feature on top of two hyper-V hosts and select the corresponding failover cluster

2. Add the corresponding failover cluster here and click "Next"

3, confirm the corresponding configuration information, click "Install"

4, the installation is complete, this time remember to need to TestServer01 and TestServer02 on the addition.

Second, configure failover centralized management

1, for the convenience of management, we add remote server Administration Tools on TESTSERVER03, install the "Failover Clustering Tool"

2, confirm the configuration information, click "Install"

3, the installation is complete.

Third, configure the iSCSI server

When configuring the cluster requires an arbitration disk, in fact, after Windows Server R2 we have a new method can not configure the quorum disk implementation cluster, here we first sell to Xiaoguanzi.

1. Tick "iSCSI target Server" on TESTSERVER03 and click "Next"

2, confirm the configuration information, click "Install"

3, the installation is complete.

Iv. Establishment of the quorum disk

1. Start configuring the quorum disk

2, open the wizard, select the TESTSERVER03 server, because we only configured a C drive here, this is just testing, so we put on the C drive, click "Next"

3. Specify the iSCSI virtual disk name and click "Next"

4, to configure the size of the quorum disk, the quorum disk does not need 2G, click "Next"

5. Here we select "New iSCSI Target" and click "Next"

6, set the corresponding target name, click "Next"

7, here we look at the corresponding TestServer01 and TESTSERVER02 server initiator name, as follows:

8, add the corresponding TestServer01 and TestServer02 IQN in the Access server, click "Next"

9. CHAP authentication is not required here, because we use Kerberos authentication, click "Next"

10, confirm the corresponding configuration information, click "Create"

11, the configuration is complete.

12, this time we can see a virtual disk is not connected state

13, we add this iSCSI virtual disk on the TestServer01 and TestServer02 server side respectively

14. Here we need to go online, initialize the disk, create a new partition, format the disk, and other operations.

Five Configure the Heartbeat line

1, the TestServer01 and the TESTSERVER02 server to configure the heartbeat line, the designated IP for 10.10.10.1 and 10.10.10.2

2, test the heartbeat between the two servers is normal.

Because of the length of the article, in the previous section, we talked about the heartbeat configuration section, and later we will explain the cluster authentication, cluster configuration, Hyper-V in the cluster with high availability features.

WIN2012R2 Hyper-V 17 configuration High availability of Hyper-V clusters (top)