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.
1. Turn off MyNode1 and MyNode2
2. Choose Virtual Disks > Create > Fixed Size Virtual Hard Disks
3. Provide Details for M Drive (250 MB) and hit "Create" button
4. Same way we would create X drive (2 GB) and Hit "Create" button.
5. Below is what you would see in Windows Explorer
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.
Click on Hard Disks
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.
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
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.
17. Choose M Drive in "Disk Parameters" screen. and finish.
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"
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
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
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
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 ID: 1030
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.
----------------------------------
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!
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..
Are you able to ping the DC from Node2? If not, try disabling firewall and check.
Regards,