Ask a questionAsk a question
 

AnswerSQL 2008 Cluster on Windows 2008 Server

  • Friday, October 23, 2009 9:08 PMgodellian Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,
    We are trying to create a 2008 SQL server cluster on windows server 2008 enterprise.  we are using 2 HP Proliant DL380 G5 servers and an MSA2012sa for our shared storage.

    when we try and create the cluster everything validates 100%, no issues.  when we try and create the cluster it gets to 'forming cluster' and then it says the operation is takeing longer than expected and eventually errors out.

    we can create a single node cluster and try and add the 2nd node to it, and it gets to the point where it says "makeing sure your node is a fully functioning member of the cluster" and then that errors out.

    anyone have any ideas?  all help is welcome.

Answers

  • Tuesday, October 27, 2009 2:41 PMgodellian Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    we finally figured it out.  we had to disable symantec endpoint protection.  shoot me now please...
    • Marked As Answer bygodellian Tuesday, October 27, 2009 2:41 PM
    •  

All Replies

  • Friday, October 23, 2009 10:10 PMMoham Mawla Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    and what is the error ?

    THX

    Please mark as answer if you think this answers your questions
  • Monday, October 26, 2009 2:04 AMZhen-Yu Zhao – MSFTMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I can't see the detailed error message. But the heads-up for the cluster beginners would be:
    1. On Win2008, the hardware and software must pass the cluster validation in failover cluster manager.(Warnings can be ignored). Seems this is done already.
    2. Create Windows cluster first, add all nodes to be clustered into it. Then create the SQL Server cluster on top of it. 
    3. The cluster and nodes must be in a domain.
  • Tuesday, October 27, 2009 2:41 PMgodellian Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    we finally figured it out.  we had to disable symantec endpoint protection.  shoot me now please...
    • Marked As Answer bygodellian Tuesday, October 27, 2009 2:41 PM
    •