Server cluster Experiment--sql cluster 4

2.7.3.  in the node2under InstallationSqlDatabase

To install the database on Node 2, you can refer to the installation of Node 1, but instead of choosing to create a new SQL failover cluster, select the SQL Failover Cluster add node

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DB/wKiom1QBokbQORWRAAJZD-9pJMA747.jpg "title=" Snap065.jpg "width=" 554 "height=" 390 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:554px;height:390px; "alt=" Wkiom1qbokbqorwraajzd-9pjma747.jpg "/>

Select "To SQL Server Failover Cluster Add node ", start Setup, install process reference node 1 installation (to ensure that the installer supports rule checking, the error cannot occur) procedure omitted

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/DB/wKiom1QBooTh2-HAAAKUv2yx4WQ516.jpg "title=" Snap066.jpg "width=" 554 "height=" 385 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:554px;height:385px; "alt=" Wkiom1qbooth2-haaakuv2yx4wq516.jpg "/>

In the case of a new database cluster, you need to specify a first owner. For specific operations see

Run Cluadmin.msc command, go to Failover Cluster Manager

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DE/wKioL1QBo8Kh3CDQAANY418QaX0461.jpg "style=" width : 554px;height:372px; "title=" Snap067.jpg "width=" 554 "height=" 372 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1qbo8kh3cdqaany418qax0461.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/DE/wKioL1QBo8LjIV86AAGuMypEACs887.jpg "title=" Snap068.jpg "alt=" Wkiol1qbo8ljiv86aagumypeacs887.jpg "/>

2.8.  Test2.8.1.  Environment

Test on a physical PC.

1. Install SQL Server 2008NativeClient 64-bit version

\\172.16.10.1\03Software\Microsoft\SQL\NativeClient\ Sqlncli_2k8_2052_x64.msi

2. Use Navicat to simulate the application

\\192.168.1.18\d$\03Software\Navicat\NavicatPremium 9.1.11 Green Edition for Windows

2.8.2.  Test

Use the tool (Navicat to simulate the application) to connect to the virtual address of the database.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DC/wKiom1QBowPj2VpAAAL46nxVc68528.jpg "style=" width : 554px;height:399px; "title=" Snap069.jpg "width=" 554 "height=" 399 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1qbowpj2vpaaal46nxvc68528.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/DE/wKioL1QBpBvDRoqBAAEjYorXZpI351.jpg "style=" width : 554px;height:423px; "title=" Snap070.jpg "width=" 554 "height=" 423 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1qbpbvdroqbaaejyorxzpi351.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/47/DC/wKiom1QBowSwaEC6AAFCjFr1Ybs875.jpg "style=" width : 554px;height:577px; "title=" Snap071.jpg "width=" 554 "height=" 577 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1qbowswaec6aafcjfr1ybs875.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DE/wKioL1QBpBvBPq9jAAHnFJ3IHDI852.jpg "style=" width : 554px;height:565px; "title=" Snap072.jpg "width=" 554 "height=" 565 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1qbpbvbpq9jaahnfj3ihdi852.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/DC/wKiom1QBowShewIQAAFZ_H7rT0U249.jpg "style=" width : 554px;height:565px; "title=" Snap073.jpg "width=" 554 "height=" 565 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1qbowshewiqaafz_h7rt0u249.jpg "/>

3.  Wrong Row3.1.  configuration not on failover Clustering feature

After clicking the "Create a Cluster" wizard link, "Browse" the server name, the host name is displayed, not the domain name, resulting in the object name cannot be found and cannot be configured

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DE/wKioL1QBpLGR113_AADN7nWy_Lc531.jpg "title=" Snap074.jpg "alt=" Wkiol1qbplgr113_aadn7nwy_lc531.jpg "/>

When you view the local User Administrators group member, the following situation also occurs

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/DC/wKiom1QBo6nRBWHeAAFiKc0dYR8501.jpg "title=" Snap075.jpg "alt=" Wkiom1qbo6nrbwheaafikc0dyr8501.jpg "/>

Troubleshooting: After joining the domain to change the network connection status, net mode changed to bridging mode, the above error occurs. Change the network connection first, then join the domain, add domain users to the local Administrators group.

3.2.  Cluster shared disk availability check failed

The cluster shared disk availability check fails when the Setup support rule runs while the SQL database is installed, see

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DC/wKiom1QBo7-goAS8AAPj02snLYY144.jpg "title=" Snap076.jpg "width=" 554 "height=" 417 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" WIDTH:554PX;HEIGHT:417PX; "alt=" Wkiom1qbo7-goas8aapj02snlyy144.jpg "/>

View the details to indicate that the cluster on this computer does not have a shared disk available.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/47/DE/wKioL1QBpPXwa7ojAACiUiLKH9s072.jpg "title=" Snap077.jpg "alt=" Wkiol1qbppxwa7ojaaciuilkh9s072.jpg "/>

This problem occurs because the disk resource owner must be Node 1 when the first node of a cluster is installed. As shown, disk resource s: The current owner is freshmannone2.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DC/wKiom1QBpAmxI8WgAALgJmaI-0o137.jpg "title=" Snap078.jpg "width=" 554 "height=" 385 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:554px;height:385px; "alt=" Wkiom1qbpamxi8wgaalgjmai-0o137.jpg "/>

Under the command line, move the cluster resource to another node.

Cluster Group " available storage "/move

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/47/DC/wKiom1QBpC6xTLGsAAHGe8qOzvg048.jpg "title=" Snap079.jpg "alt=" Wkiom1qbpc6xtlgsaahge8qozvg048.jpg "/>

Reference: How can I move Storage in Windows Cluster 2008

http://sqlserver-help.com/2011/06/11/help-how-can-i-move-storage-in-windows-cluster-2008/

3.3.  Network binding Order

Click on the "Network binding order" warning link to view the alert

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/DC/wKiom1QBpEyDG1b6AACzOzPrQm4434.jpg "title=" Snap080.jpg "alt=" Wkiom1qbpeydg1b6aaczozprqm4434.jpg "/>

This warning occurs because the domain network is not the first bound network. However, the binding order has been adjusted in the previous operation. Review again, no problem

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DE/wKioL1QBpXmRi7HNAAFs9kIg3i8968.jpg "title=" Snap081.jpg "alt=" Wkiol1qbpxmri7hnaafs9kig3i8968.jpg "/>

Finally, after installing the cluster software, the operating system has a hidden virtual network card, the name of this NIC is microsoftfailover Cluster virtual Adapter.

With the Ipconfig/all command, you can see the NIC.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DC/wKiom1QBpHPTiQhHAAKqVK-elsY395.jpg "title=" Snap082.jpg "width=" 554 "height=" 385 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:554px;height:385px; "alt=" Wkiom1qbphptiqhhaakqvk-elsy395.jpg "/>

Solution:

1. Get the UUID of this virtual net

2. Modify the order of network bindings in the registry.

C:\>wmicnicconfig Get description, Settingid

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/DC/wKiom1QBpJ3iCTMeAARnq1T02LE170.jpg "title=" Snap083.jpg "width=" 554 "height=" 596 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:554px;height:596px; "alt=" Wkiom1qbpj3ictmeaarnq1t02le170.jpg "/>

The UUID for this NIC is {B87d7f52-9ee9-4cca-9eb9-3431f5ccabb}, and the order of bindings is modified by registering the editor.

Run the regedit command to enter the registry editing interface

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/47/DC/wKiom1QBpObjahfOAAJ-MCTIhrw323.jpg "title=" Snap084.jpg "width=" 554 "height=" 379 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" WIDTH:554PX;HEIGHT:379PX; "alt=" Wkiom1qbpobjahfoaaj-mctihrw323.jpg "/>

Hkey_local_machine\system\currentcontrolset\services\tcpip\linkage under Bind, double-click to edit. Moves the cut to the last.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/DE/wKioL1QBpmGwE8BpAAEO4OK_5ME243.jpg "title=" Snap085.jpg "alt=" Wkiol1qbpmgwe8bpaaeo4ok_5me243.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/47/DC/wKiom1QBpUryUqJVAAEDw6nD3GM301.jpg "title=" Snap086.jpg "alt=" Wkiom1qbpuryuqjvaaedw6nd3gm301.jpg "/>

Reference:

http://support.microsoft.com/default.aspx?scid=kb; en-us;955963

Microsoft failoer Cluster Virtual Adapter

To resolve this issue, remove disabled or ghostednetwork adapters. To does this, follow these steps:

At a command prompt, type the following commandlines:

Set Devmgr_show_nonpresent_devices=1

Start Devmgmt.msc

Start ncpa.cpl

Note make sure, that's press ENTER after Eachline.

In Device Manager, expand Network Adapters.

Compare the list of network adapters in DeviceManager to the list of the network adapters that is displayed in Networkconnect Ions. Network adapters that is present in Device Manager and not innetwork Connections is ghosted network adapters.

If There is any disabled the network adapters, Enablethese adapters in Device Manager or in Network Connections.

If There is any ghosted the network adapters, Removethem in Device Manager.

Start SQL Server Setup.

After Setup was complete, the open Network Connections,and then disable the any Network adapters so you does not want.

3.4.  WindowsFirewall

Click on the "Windows Firewall" warning link to view alerts

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/47/DC/wKiom1QBpXizDCkHAADEId-IIKs114.jpg "title=" Snap087.jpg "alt=" Wkiom1qbpxizdckhaadeid-iiks114.jpg "/>

In the lab environment, you can turn off the firewall to resolve this warning message, but you need to set the appropriate port information in the production environment to resolve this issue

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/47/DE/wKioL1QBpp_TbBHnAAJ2VZVT3R8265.jpg "title=" Snap088.jpg "width=" 554 "height=" 385 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:554px;height:385px; "alt=" Wkiol1qbpp_tbbhnaaj2vzvt3r8265.jpg "/>

This article is from the "high pine-Elf on the Road" blog, please be sure to keep this source http://gaoxin1993.blog.51cto.com/9151134/1547112

Server cluster Experiment--sql cluster 4