How to create SQL Server 2005 Clustering with Virtual Server 2005 (Part 5)

How to create SQL Server 2005 Clustering with Virtual Server 2005 (Part 5)

Rate This
  • Comments 66

This is the last part of the series. Once you have configured windows cluster and MSDTC, installing SQL is piece of cake. I already mentioned in part 1 that you have to download ISO (SQLEVAL.ISO) which we would need to attached as CD drive which would have setup files. I have copied the image on E:\Virtual Server\SQLEVAL.ISO

We also need to create domain account and domain groups in domain controller.  So, logon to domain controller. Go to Start > Run > DSA.msc and follow below screen-shots.

AD Users and Computers

Give the details of account (i.e. SQLSVC)

 SQLSVC Account

Set the password after clicking next button. Make sure that "Password never expires" is checked and "User cannot change password" is checked.

SQLSVC Account Password

One account is created, lets add a Group and add SQLSVC into the group.

SQLSVC New Group

Give Group Name "SQL Admin Groups"

SQLSVC Group Name

Right click on  "SQL Admin Groups" properties and add "members"

SQLSVC New Group Members

Now you are done with Domain controller.

Now, let's mount ISO image to MyNode1 and MyNode2. To do this, go to Virtual server console.

CD_DVD

Click on CD/DVD and fill details as below

CD_DVD_Properties

Above has to be done on both the nodes. Once you do that, you can see SQL Installation CD mounted on MyNode1 and MyNode2.

Lets Start SQL setup now.

  1. Log off from MyNode2. This is required to avoid running into known bug.
  2. Log on to MyNode1.
  3. Move all the resource groups to MyNode1 using Cluster AdminMyNode1 Active Groups 
  4. Go to DVD drive and double click on setup.exe from Servers folder
  5. Accept EULA. Next.
  6. Click 'Install' and wait for SQL Server to configure components and setup the installation. Once the required components (.NET Framework 2.0, MS SQL Native Client and the SQL Server 2005 setup support files) have been installed click 'Next'
  7. Click 'next' when prompted with the screen 'Welcome to the Microsoft SQL Server Installation Wizard. The installation will then proceed through the 'System Configuration Check'- click 'next' to proceed.
  8. Enter Registration Information, click 'next'
  9. Components to Install- Select all components (SQL Server Database Services, Workstation components) , then click 'next' components to install 
  10. Since this is the first installation of a new database instance for SQL server, select 'Default Instance'.
  11. Provide Virtual Server Name (VirtualSQL) VirtualSQL
  12. Provide Virtual SQL Server IP Address (192.1.1.6) in Next screen and click on Add. Then Next   
  13. VirtualSQLIP
  14. Provide SQL Group in Next screen as shown below Cluster Group Selection
  15. Click Next on Below Screen
  16. Select Nodes
  17. Provide Administrator Password in next screen and click Next
  18. Provide SQL Service Account created earlier on domain controller(sqlsvc) SQLSVC Provide
  19. Provide Domain Group which we created earlier (SQL Admin Groups) SQLSVC Group Provide
  20. Authentication Mode. Choose Mixed Mode (Windows Authentication and SQL Server Authentication), provide sa password and click 'next'
  21. Keep the default settings (SQL Collations- Dictionary Order, case-insensitive, 1252 character set) and click next
  22. Error and Usage Report Settings. Leave defaults (none checked). Click 'next'
  23. Check installation Settings, click 'install'.
  24. During the install process you can always see what is happening on other node.
  25. Once the installation process is completed, click 'next'
  26. And finally... Finish.

Now we are done with the setup and we should see the resources in cluster admin under SQL Group.

Any feedback is greatly appreciated.

Leave a Comment
  • Please add 5 and 1 and type the answer here:
  • Post
  • Great document! I was getting a problem with MSDTC failing at failover, your MSDTC guidance got that fixed.  Thanks

  • Great series! Thank you for the work you put into all five articles!

    One question: you mention the previous creation of the user, sqlsvc, and the group,SQL Admin Groups. But I cannot find that reference anyway else in the series. Are there any specifics to their creation? This is exactly where sql setup is failing on me, as it cannot 'see' and verify either the user or the group.

    Any help would be appreciated.

    Regards,

    Rick Hinze

  • Hi Rick,

    Thanks for the feedback. I have added details to created domain account and group in the beginning of 5th part of series. Hope you will find it useful

    Regards,

    Balmukund

  • Hi

    I am still child in this tech, i am using you r document to complete my cluster installation

    thank you so much if i need u r help i will ask u definetly , i think u will not say no to help in this

    thank you

    Satish

  • Hi Satish,

    Thanks for the comment. Feel free to ask question on this blog and I will reply to them as soon as possible.

    Thanks,

    Balmukund

  • ALl I can say is youve given me something to do over the weekend and Im thankful for it!

    Thanks for sharing your knowledge mate.

  • Hi Jide,

    I am happy to hear that you would be using my blog to learn something new and help your business grow.

    In case, you feel you need help please feel free to comment and I will reply them ASAP (unless I am not sleeping)

    Thanks,

    Balmukund

  • part 5 step 1 mentions log off node2. When should this node be re-started and re-logged on?

    Excellent article and well worth the study.

    Thanks

  • Hi William,

    Thanks for the feedback.

    This step is required as work around of issue mentioned in KB.

    http://support.microsoft.com/kb/910851/en-us

    Once SQL Setup is complete, you can log back in.

    Did I answer your question?

    -Balmukund

  • Hi Balmukund,

    Thank you very much for guide.

    Really an EYE Opener for me regarding the virtual HD stuff as it eliminates the third party iSCSI Target software.

    Thanks again!

    br,

    Robin

  • Hi Balmukund,

    Nice article, I've tried it on my virtual server. The system Configuration Check is success , but in the last part I always got an errors when tried to install SQL 2005,

    Microsoft SQL Server 2005 9.00.1399.06

    ==============================

    OS Version      : Microsoft  Windows Server 2003 family, Enterprise Edition Service PACk 2 (Build 3790)

    Time            : Mon Feb 2009

    SQLNODE1 : The current system does not meet the minimum hardware requirements for

    this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.

    Task did not appear to start on machine: \\SQLNODE2

    My cluster admin just doing fine, both of node bring online.

    JFYI my VS node spec is:

    -RAM 512

    - Shared disk : 16 GB for system (C), 3 GB for Data (X), 512 MB for Quorum(Q) and 512 MB for MSDTC (M)

    Do you have any suggestion?

    Thanks,

    Rama

  • As per error it looks like you are running setup from SQLNode1. So few things to check..

    1. If you are running setup from CD disk (ISO Image), make sure that you able to access \\SQLNODE1 from SQLNODE2 and the setup files share. It would be better if you can copy the setup files on C drive and then run the setup.

    2. Make sure all sessions are logged off from SQLNODE2. There is a bug in SQL Setup which will cause setup to fail if you have any session open on remote node. http://support.microsoft.com/kb/910851/en-us

    Let me know if it does not help.

  • Hi,

    Thanks, that's a good idea, I've tried to copy source CD to C:  and running setup smoothly till finish :)

    A few to ask, after setup finish if i opened the SQLNODE2 i can't find the shared disk (Q , M or I), from device management i found unknown/unreadable for 3 shared disk except C: . Is that a normal condition?

    And how to test SQLNODE1 fail over to SQLNODE2?

    Many thanks for the answer.

    Rama

  • That's the behaviour of cluster (share nothing model). Disk would be visible to the node which owns the disk.

    To test failover, you can open cluster Administrator (start>run>cluadmin) and do "Right click, Move Group" on SQL Group to check failover.

    Thanks

    Balmukund

  • Such a beautiful article, what a beautiful explanation, WOW. Nice job balmukund keep it up.

Page 1 of 5 (66 items) 12345