locked
How to manage windows cluster on windows server 2008 R2 RRS feed

  • Question

  • Hi I want to know how to properly shutdown or stop windows cluster with out failover or  failing it.

    I have successfully created windows cluster on win 2008 R2 sp1 using vmware with starwind software for SAN storage.

    Now when I  shut down or stop cluster service on node1 it failsover and shows critical errors fine.ok... I tried to destroy and clean up cluster  using cmd commands.Forcecleanup both nodes with cmd commands.it was successful.

    Later I recreated san storage with target and initiator configuration using starwind without any issue.

    I Reinstalled FC service on both the nodes restarted vmnodes.I cheked all the firewall were disable.and machines able to ping well..

    Now when I tried to recreate new cluster it fails and gives different errors.AS  Node1 was evicted from cluster,Another was Quoram was lost as no witness disk was found.
    Also It did not show my cluster under FCM on Node2.I tried to add node Node2 but error saying Node2 is already in a cluster.
    So I want to know how to manage windows cluster properly and manage it entries in active directory so that even after shutting/stopping the service/destroying cluster I do not need to do all over again.

    I had to recreate all VMware from start and do AD setup and SAN storage again then only windows cluster got successfully created once again....................

    I had to recreate all vmware nodes with FC sevice reinstalled and also recreate AD DS and DNS.


    srm_2010

    Sunday, January 4, 2015 3:39 PM

Answers

  • Hi srm_2010,

    You can refer the following KB:

    Start or Stop the Cluster Service on a Cluster Node

    http://technet.microsoft.com/en-us/library/cc771742.aspx

    I’m glad to be of help to you!


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    • Proposed as answer by Alex Lv Friday, January 9, 2015 9:01 AM
    • Marked as answer by Alex Lv Monday, January 26, 2015 8:53 AM
    Thursday, January 8, 2015 9:25 AM

All replies

  • Hi! StarWind support is here!:) 

    Regarding Quorum loss: it looks like missconfiguration issue here. I`d double check if you configured MS initiator properly. Quorum should be connected through the loopback only on each node participating in cluster. BTW, since this question is StarWind related you can post it to StarWind forum

    Regarding new cluster isues: I faced such behaviour once, and it was somehow related to the fact that not all the records about the cluster was erased from domain. I worked around that by using different names for cluster and for the nodes. 


    • Edited by AnatolySV Tuesday, January 6, 2015 1:53 PM
    • Proposed as answer by VR38DETTMVP Tuesday, January 6, 2015 6:05 PM
    Tuesday, January 6, 2015 1:51 PM
  • Hi srm_2010,

    You can refer the following KB:

    Start or Stop the Cluster Service on a Cluster Node

    http://technet.microsoft.com/en-us/library/cc771742.aspx

    I’m glad to be of help to you!


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    • Proposed as answer by Alex Lv Friday, January 9, 2015 9:01 AM
    • Marked as answer by Alex Lv Monday, January 26, 2015 8:53 AM
    Thursday, January 8, 2015 9:25 AM