Author: Sanjay MishraContributors: David P Smith (ServiceU)Reviewers: Chuck Heinzelman, Mike Weiner, Prem Mehra, Kevin Cox, Jimmy May, Min He
Installing a SQL Server Failover Cluster Instance (FCI) usually involves performing a setup on the first node, and after that, running setup to ADD NODE on the other node(s) in the FCI. A recent SQLCAT lab engagement required a 4-node FCI; and, with the intention of saving overall setup time, we tried to be “smart” by:
After the concurrent setups on Node3 and Node4 were complete, we looked at the properties of the FCI, and what we saw surprised us. Node3 was missing from the possible owners list of all the resources. We expected the possible owners list to be Node1, Node2, Node3, and Node4, but what we saw were Node1, Node2, and Node4 listed as possible owners, but not Node3.
After further analysis, we discovered what happened during the concurrent setup on Node3 and Node4.
Expected result: Possible owners=Node1, Node2, Node3, Node4
Upon further research, we found out that SQL FCI setup is not designed for concurrent setups on multiple nodes of an FCI. In fact, concurrent setup on multiple nodes of an FCI is not a supported operation. The correct approach to install this multi-node FCI is: