SQL Server high-availability failover (2)

Add Network card Heartbeat line

Target: Two SQL Servers need to add network card heartbeat line for SQL Server internal data transfer

Computer name	IP information	Heartbeat line
Hsr1	192.168.2.5 0    (IPv4 IP) 255.255.255.0   (mask) 192.168.2.1     (Gateway) 192.168.2.52    (DNS)	100.100.100.1  (IPv4 IP) 255.255.255.0  (Mask Does not need to configure the gateway and DNS
HSR2	192.168.2.51 255.255.255.0 192.168.2.1 192.168.2.52	100.100.100.2 255.255.255.0 No need to configure gateways and DNS

First HSR1 Configure the heartbeat line, open VM virtual machine configuration

After adding, rename the entry system

Change the heartbeat line NIC properties, because the network is mainly used for data transmission, it is recommended to cancel all services outside of TCP/IP4. Keep the following status

Configure heartbeat Address: 100.100.100.1 255.255.255.0; no need to configure gateways and DNS

Click Advanced options; Switch to DNS tab: Uncheck: Register this connection's address in DNS

Then switch to the WINS tab: Uncheck: Enable LMHOSTS lookup, disable the NetBIOS feature on TCP/IP, confirm

Then change the network priority order;

In a network connection----Click organize----TICK menu----advanced----Local Area Connection priority higher than heartbeat line

Second HSR2 Configure the heartbeat line to open the VM virtual machine configuration

The steps are set in the same way as the first one, except

Configure heartbeat Address: 100.100.100.2 255.255.255.0; no need to configure gateways and DNS

Note: To set up two SQL Servers to enable IPv4 echo, otherwise the IP and heartbeat line of the other cannot be spelled

Inbound Configuration

Outbound Configuration

When you are done, test the two heartbeat lines to get through each other.

HSR1 IP 50 Heartbeat line is 100.100.100.1 HSR2 IP 51, heart jumper 100.100.100.2

Re-test IP 50 to spell the other IP 51 address

In turn 51 spell 50

SQL Server high-availability failover (2)