"Win Server" those days to build clusters and SQL AlwaysOn stepping on the Thunder ...

It's a sad blog.

Because the last few days have been tossing cluster configuration and AlwaysOn, stepping thunder there are several, but the dead have not succeeded now ...

Building an AlwaysOn environment requires:

1. Windows Server2012 Datacenter Version (because failover clustering is supported)

2. Each service node plus domain, it seems that AlwaysOn maximum support 3 nodes, according to small cost considerations, two servers bar. Here I choose the Dell R730, double E5

3. Shared storage (for the quorum witness of the cluster), if it is an odd node configuration, you need to share the storage, even if you share the folder. Here you choose to use a common Dell 3010 standalone to create a shared folder to resolve.

4. A domain controller, here I use a virtual machine to solve. (production environment do not put the domain control and quorum witness shared storage together)

The steps of the Thunder include the following:

1. Establish the domain environment problem (first time is not to listen to the advice, directly put the domain control on Node A, quenching)

2. SQL cannot be accessed via Windows authentication on the intranet in a dual network segment environment, AlwaysOn configuration quenching

3. Change the single network environment, directly changed the domain control IP, the physical node IP (that is, disabled the original intranet network card), shared storage IP, the result of failover group access problems (originally set up the network from the access, directly to the external network after quenching)

4. Retire the cluster and rebuild the failover cluster (the first time is reported, the configuration is hung up, because there are nodes that fail the cluster)

5. Clear-clusternode Tool failed (no solution)

6. According to a blog post, killed the cluster related two registry entries, the rebuilding of the cluster even verification is not over.

7. Re-install Node A, after the completion of the cluster, found that actually B also completely hung up (currently re-installed Bing)

The above problems in turn to record some analysis and solve the idea of tip

1. Domain control must be independent, because all domain account validation is implemented by it.

2. In fact, later thought, if the first only to an intranet network Jianjian cluster, instead of using a dual network segment configuration, first put AlwaysOn configuration up on the right. Just consider that on the two servers, there must be an external network access for a data acquisition middleware to work correctly, I did not think of this.

There is no doubt about the fact that SQL Server does not support multiple NICs. However, it appears that the domain account is only able to receive the routing communication of a single network card, resulting in the use of IP address +sa account login is not a problem, Windows computer name +windows authentication is only valid on one network segment, the other is over-the-times error. (and the error is not accessible)

3 colleague also did this, but he started with a single network segment configuration, so directly changed to no problem, I guess I have a problem here is because the original configuration has two network records, so directly changed the domain network segment, cluster address, the cluster to two nodes of the communication is broken. The retreat group is more to avoid talking. I didn't think of it at first, so I went on a detour. (Sure to take the environment to spell character)

Comprehensive analysis down, the retreating group must be done without destroying the original cluster structure, the direct call cleanup should be able to not reload.

4. The upper hole causes the fallback group to be invalid and the cluster cannot be cleaned properly.

5. Clear-clusternode Tool error is unable to load a DLL this type of error, according to the experience of software development, either itself Windows environment is not complete, or the parameters are not correct. Unfortunately this parameter user can not be modified, Bing and Baidu is also no solution. (Everyone has a good luck ...) ）

6. In fact, 456 of the mines are chained. These operations are not valid because the cluster is hung.

Must be cautious. Careful clustering ... Hey.....

"Win Server" those days to build clusters and SQL AlwaysOn stepping on the Thunder ...