Share via

sql server cluster setup question.

Heisenberg 266 Reputation points
2021-11-11T22:21:54.937+00:00

We are having some issues with our existing cluster setup. Currently we have 2 node cluster setup and it is having some issues, it doesnt failover correctly. So what we are planning is

add 2 more nodes one after another. For instance add node #3, test if failover is happening correctly and then remove node #1, then add one more node and test the failover and then remove the 2nd old node. This way we will finally have only 2 newly added nodes.

Will these steps work.

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

0 comments No comments

2 answers

Sort by: Most helpful
  1. Heisenberg 266 Reputation points
    2021-11-12T17:32:37.923+00:00

    @AmeliaGu-MSFT thank you for your response. I was under impression when you install cluster from scratch, first node has more binaries installed as compared to other nodes. That is why i was hesitant to use this approach. So as per your answer, i dont think there is any dependency like that.

    Issue we are having in our current cluster is- Our current application has hardcoded ipaddress and there are lots of unknown areas in the application where we dont know this ipaddress is hardcoded. To workaround this what we do is we have a custom failover vbscript whereby when cluster fails over we assign the same ipaddress to the secondary node's nic card where cluster will failover. This way virtual ipaddress and sql cluster name remains same even after failover. This approach is working fine in our DR environment however not in production.

    We see ipaddress assignment is happening correctly on secondary server nic card in PROD however cluster fails to bring sql server resources online. We are thinking there might be some setup issue with the sql cluster install beause of which failover is not happening. Hence we are going to rebuild this cluster the way i explained above.

    Steps

    1. Add 3rd node in wsfc , then add a node in sql server using setup.
    2. if failover to 3rd node is happening correctly, then remove 1st node from the cluster
    3. then add another node in wsfc and sql server. if failover is happening correctly to this newer node then remove old second node from the cluster.

    is there a better approach to this?

    Was this answer helpful?

    0 comments No comments

  2. AmeliaGu-MSFT 14,016 Reputation points Microsoft External Staff
    2021-11-12T07:42:00.67+00:00

    Hi SQLServerBro,
    I think the steps will work.
    Please check this doc which might be helpful.

    Currently we have 2 node cluster setup and it is having some issues, it doesnt failover correctly.

    Are there any error message about this issue?

    Best Regards,
    Amelia


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.