Changing the server cluster IP and database Alwayon listening IP

Currently the database server has three, the operating system version of Windows Server R2 with SP1, the database version is SQL Server standard R2, three database server computer name and IP address are as follows:

sqlsrv-001:10.0.0.11,

sqlsrv-002:10.0.0.12,

sqlsrv-003:10.0.0.13,

Server cluster IP is 10.0.0.10, database listening IP is 10.0.0.15

For business needs, it is now necessary to change all IP addresses, change the method to refer to the online search information, the actual change process confirms that the following methods are effective.

First step: Change the IP address of the sqlsrv-001 to 10.0.0.21

Method: Directly change the NIC properties and confirm.

Impact: Database AlwaysOn group, will show sqlsrv-001 error offline, about 2 minutes or so, and return to normal.

Step Two: Change the IP address of the sqlsrv-002 to 10.0.0.22

Method: Directly change the NIC properties and confirm.

Impact: Database AlwaysOn group, will show sqlsrv-002 error offline, about 2 minutes or so, and return to normal.

Step three: Change the IP address of the sqlsrv-003 to 10.0.0.23

Method: Directly change the NIC properties and confirm.

Impact: Database AlwaysOn group, will show sqlsrv-003 error offline, about 2 minutes or so, and return to normal.

Fourth step: Delete and create an AlwaysOn group's listening IP, the new listening IP is 10.0.0.25

Method: On the primary database, delete the listening IP directly, and then add the listening IP.

Impact: The AlwaysOn group returns to normal for approximately 2 minutes after the new listening IP is added.

Fifth step: Change the server cluster IP address, the new cluster IP is 10.0.0.20

Method: Open the Cluster management interface, click on the left directory in the cluster, the right middle section, there is a group is the core resources of the cluster, expand after you can see the cluster's IP address information, click Properties, and then modify the IP address, after the modification is completed, remember to let the cluster offline, and then online, it can take effect.

Impact: The cluster fails during the change process and returns to normal after it is brought back online.

This article does not, if in doubt can reply me.

This article is from the "brave" blog, make sure to keep this source http://brave8898.blog.51cto.com/289041/1961963

Changing the server cluster IP and database Alwayon listening IP