Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
What is correct way to evict a sql cluster node

Answered What is correct way to evict a sql cluster node

  • Monday, February 04, 2013 7:40 AM
     
     
    Sign In to Vote
    0

    Hi,

    One of our sql cluster node is unable to start. So will decide to evict, please help correct way to do it.

    DO I:

    1. first do this http://msdn.microsoft.com/en-us/library/ms191545%28v=sql.90%29.aspx
    2. remove the failed node as possible owners of resources in cluster administrator
    3. then evict the failed node from cluster administrator

    Thanks,
    Luanne

     

All Replies

  • Monday, February 04, 2013 8:04 AM
     
     
    Sign In to Vote
    0
    http://msdn.microsoft.com/en-us/library/ms191545.aspx

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Blog: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance

     
  • Monday, February 04, 2013 1:38 PM
     
     
    Sign In to Vote
    0
    Eviction is all you need to worry about. You should not need to make all those other configuration changes you mention especially if you will be adding a rebuilt node of the same name into the cluster. If not, then you can easily perform any required cleanup post removal, but from a functional perspective this should not be needed.

    Regards,
    Mark Broadbent.

    Contact me through (twitter|blog|SQLCloud)
    Please click "Propose As Answer" if a post solves your problem
    or "Vote As Helpful" if a post has been useful to you
    Watch my sessions at the PASS Summit 2012

     
  • Monday, February 04, 2013 10:09 PM
     
     Answered
    Sign In to Vote
    0

    What version of SQL Server? For 2005 and earlier, you cannot just evict a node from the WSFC without possible consequences to SQL Server. You have to change the definition according to SQL Server (i.e. re-run Setup and remove it from the definition). Then you can evict from the WSFC.

    For SQL Server 2008 and later, you can just evict the node from the WSFC and SQL will work just fine.

    Allan Hirt Blog: http://www.sqlha.com/blog Coming in 2013: Mission Critical SQL Server 2012 - the followup to Pro SQL Server 2008 Failover Clustering



     
  • Tuesday, February 05, 2013 7:46 AM
     
     
    Sign In to Vote
    0

    Okay, so it seems my steps are correct:

    1st step: I will remove the failed node following the steps here.

    2nd step: in cluster administrator screen i will remove the failed node as possible owners of resources (if still exist there)

    3rd step: in cluster administrator screen i will evict the failed node.

    Next question... the failed node can't be turned on, can I do 1st step from the current active node?

    Thanks,
    Luks

     
  • Tuesday, February 05, 2013 8:39 AM
     
     Answered
    Sign In to Vote
    0

    No, not really.

    1. You have to run Step 1 on 2005 from the node that owns the instance. You never run it from the node you can't get to or want to evict unless it is the last node and you want to uninstall your 2005 instance.

    2. You don't remove the node as a possible owner of anything SQL or any resources - that's why you do your Step 1 for SQL and then when you do your step 3, it removes it from thw WSFC. So your Step 2 is not necessary at all.

    Allan Hirt Blog: http://www.sqlha.com/blog Coming in 2013: Mission Critical SQL Server 2012 - the followup to Pro SQL Server 2008 Failover Clustering

     
  • Tuesday, February 05, 2013 8:44 AM
     
     
    Sign In to Vote
    0

    Hi Allan,

    node1 = failed node
    node2 = ok node. the current node holding the sql instance

    Yes, since my node1 cant be turned off then I will execute step1 from node2.
    next will do step3. step2 is skipped.

    Okay, I will try this one and will come back here. :)

    Thanks everyone!

    Luks

     
  • Wednesday, March 06, 2013 12:05 AM
     
     
    Sign In to Vote
    0

    Follow-up question...

    Do I need to stop the sql server service if I need to evict a node using step1 above?

    Thanks,
    Luks

     
  • Monday, March 11, 2013 12:41 AM
     
     
    Sign In to Vote
    0

    Okay, as I mentioned one of our cluster nodes cannot go online.

    I did tried to remove it from the SQL as one of the nodes but it appear under Unavailable so I don't have any way to evict from that side.
    What I did next is evict it from windows cluster, no corruption in all my nodes. We will try to add this node back when it can go online.

    Thanks to all.