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

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

Rate This
  • Comments 20

In previous parts(Part 1, Part 2 and Part 3), we have completed windows clustering. Now, before installing SQL Cluster we have to configure MSDTC. We also need to make some shared drive which we would use to keep SQL Server databases and MSDTC. We are going to use Disk M for MSDTC and Disk X for SQL Server. We have already done the steps for Disk Q in part 2 (Create Quorum Disk section). I will reproduce the steps for Disk M and X here.

Configure Shared Disks

1. Turn off MyNode1 and MyNode2

2.  Choose Virtual Disks > Create > Fixed Size Virtual Hard Disks

Create Virtual Disk(M Drive)

3. Provide Details for M Drive (250 MB) and hit "Create" button

Create Virtual Disk(M Drive) Details

4. Same way we would create X drive (2 GB) and Hit "Create" button.

Create Virtual Disk(X Drive) Details

Create Virtual Disk(Y Drive) Details

5. Below is what you would see in Windows Explorer

All Disks

6. Lets attach the disks to MyNode1 and MyNode2 (They are off at this moment) I am showing for MyNode1. Please follow same for MyNode2 also.

MyNode1_Edit Configuration

 MyNode1 Edit hard disk

Click on Hard Disks

MyNode1 HardDisks Properties

Hit OK and it would attach the disks to MyNode1. Follow the same for MyNode2

7. Turn on ONLY MyNode1.

8. Login to MyNode1 and Start > Run > DiskMgmt.msc. Cancel on the screen if you get any.

9. You should see two new Disks which are Not Initialized. Right Click and choose Initialize Disk.  Then you create partition by Right Click New Partition. Below is final screen shot which you should see.

MyNode1 Disk management

10. Now Turn Off MyNode1 and Turn On MyNode2

11. Go to DiskMgmt.msc on MyNode2 and assign drive letters (M for 250 MB drive and X for 2 GB Drive)

12. Open Cluster Administrator (Start > Run > CluAdmin)

13. Create New Group called MSDTC (File > New > Group) and provide details

New Group MSDTC

14. Choose Both Nodes as preferred owner. You might get an error at last screen but that's OK because MyNode1 is offline.

15. Create a new "Disk" resource under MSDTC Group (File > New > Resource) Choose details as below screen shot.

New Resource M Drive

17. Choose M Drive in "Disk Parameters" screen. and finish.

Disk Parameters

18.  Now you should see a Disk resource under MSDTC Group. Right click and choose "Bring Online"

19. Follow 13 to 18 again to Create new groups called "SQL Group" and add "Disk X"

SQL Group Online

20. Up to here we have completed shared disk configuration for MyNode1 and MyNode2. Let's start MyNode1 and test fail over for new groups.

21. Before we install SQL Server, we have to configure MSDTC

Configure MSDTC as Resource

  1. On MyNode1 and MyNode2 follow below steps
    • Open Control Panel on the cluster node
    • Double-click Add/Remove Programs
    • On the left side of the screen, double click Add/Remove Windows Components
    • Under Components, highlight Application Server and click Details
    • Select Enable network DTC access, and then click OK
    • Click Next
    • Click Finish
  2. Add "MSDTC IP Address resource" in MSDTC Group
    • Right click MSDTC Group and select New > Resource
    • Type a some name such as MSDTC IP Address
    • In Resource Type, choose IP Address
    • Click Next
    • Click Next on Possible Owners screen
    • Click Next on Dependencies Screen
    • Give IP Address as 192.1.1.5
    • Click Finish
    • Right click the MSDTC IP Address resource and select Bring Online.
  3. Add "MSDTC Network Name" resource in MSDTC Group
    • Right click MSDTC Group and select New > Resource
    • Type a some name such as MSDTC NN
    • In Resource Type, choose Network Name
    • Click Next
    • Click Next on Possible Owners screen
    • On Dependencies Screen, move MSDTC IP Address and click on Add to bring on Right window. Now hit Next.
    • Give Name as MSDTC
    • Click Finish
    • Right click the MSDTC NN resource and select Bring Online.
  4. Add "MSDTC" resource in MSDTC Group
    • Right click MSDTC Group and select New > Resource
    • Type a some name such as MSDTC
    • In Resource Type, choose Distributed Transaction Coordinator
    • Click Next
    • Click Next on Possible Owners screen
    • On Dependencies Screen, choose "MSDTC NN" and "M Drive" and click on Add to bring on Right window.

                        MSDTC Dependencies

    • Click Finish
    • Right click the MSDTC resource and select Bring Online.

MSDTC Group Online

Above is the screen shot of "MSDTC group". Make sure you have matching "Resource Type" as shown in the screen.

Test fail over for MSDTC group. This finishes all Prerequisites to install SQL Server on Cluster. Get ready to install SQL Server in last part of the series.

You can follow http://support.microsoft.com/kb/899191 to make changes to MSDTC Services.

Lets move on to last part of the series

Leave a Comment
  • Please add 5 and 1 and type the answer here:
  • Post
  • Hi Kishore,

    If you turn off Node1, you should be able to access cluster administrator which would show Node1 as red cross (means cluster is not able to access that node) Could you please check if cluster service is started on Node2 or not.

    Coming to failover question, if you turn on Node1 back (assuming resources are one Node2) cluster would NOT attempt to bring it back to Node1 unless you have configured failback in group properties.

    Reason: Moving resource back would be another downtime and you may not want to do that in business hours. Failback can be set to "immedietly" or "between x to y" time.

    Hope this answers your question.

    Balmukund

  • Thanks Balmukund..Your Failback really answers my questions..regarding Cluster service.Here is what i did with Cluster Installation process..I followed the steps and installed new cluster service on Node1(192.168.1.118) first and added Node2 to the existing cluster.When i turned off Node1 this what it's happening when i simulated the same..

    1.) As you mentioned now i can see red sign on Node1 & i can browse Node2 info..

    2.) I see all the resources & shared drives are available on Node2 with status "Online", but i see "Cluster IP Address" -- Failed

    "Cluster Name" --  Offline status and i see cluster service is started in Node2 -Automatically.In Node i see the following Error Messages in Event Log/Also i have some screen shots i can share with you.If you don't mind can you send me an email to kishore76athotmail.com:

    -----Error Messages Node2---------

    Event Type: Error

    Event Source: Userenv

    Event Category: None

    Event ID: 1058

    Date: 12/22/2009

    Time: 8:47:12 AM

    User: KKE\Administrator

    Computer: MYNODE2

    Description:

    Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=KKE,DC=local. The file must be present at the location <\\KKE.local\sysvol\KKE.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (The network path was not found. ). Group Policy processing aborted.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    ---------------------

    Event Type: Error

    Event Source: Userenv

    Event Category: None

    Event ID: 1030

    Date: 12/22/2009

    Time: 8:47:12 AM

    User: KKE\Administrator

    Computer: MYNODE2

    Description:

    Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    ----------------------------------

  • Looks like machine is not able to access domain controller when it was trying to start cluster service

    Below error says - network path not found.

    \\KKE.local\sysvol\KKE.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (The network path was not found. ).

    Hope this helps!

    Balmukund

  • Yes I checked that one..Looks like Node2 is unable to see DC's GPO.I tried to just type this command in Node2 --> RUN ..i get the same error.But gpt.inifile is located in DC.Any idea how to resolve this issue..In my case i used DC's administrator account to login to both Node1 & Node2..Pl's let me know if you have any idea..

  • Hi Kishore,

    Are you able to ping the DC from Node2? If not, try disabling firewall and check.

    Regards,

    Balmukund

Page 2 of 2 (20 items) 12