crazywolf2010
asked on
Building MS SQL Server 2008 x 3 node cluster under Windows 2008
Hi All,
I am looking for a step-by-step document else process which details how to build a 3 node ACTIVE-ACTIVE SQL server 2008 cluster.
I am new to windows clustering /SQL server clustering. I am looking for all details to start after windows OS install till successful failover testing.
Please do not post MS docuemnt URLs. I can find them myself. I am here to find a real life example.
Thanks
I am looking for a step-by-step document else process which details how to build a 3 node ACTIVE-ACTIVE SQL server 2008 cluster.
I am new to windows clustering /SQL server clustering. I am looking for all details to start after windows OS install till successful failover testing.
Please do not post MS docuemnt URLs. I can find them myself. I am here to find a real life example.
Thanks
ASKER
Hi,
How do I do it?
How do I do it?
Is the OS 2008 or 2008 R2?
This link describes a SQL install:
http://msdn.microsoft.com/en-us/library/ms179530.aspx
One should build a file server to become familiarize with 2008 clustering. 2008 clustering has some AD requirements that 2003 did not have.
Once the cluster is created and the nodes have been added to the cluster, then SQL would be installed (3 times) so each instance of SQL would have a set of shared disk, a network name and an IP address.
Should end up with: Default cluster group with an IP, network name and the quorum drive.
SQL instance 1 group with again IP, network name and SQL data disk(s)
SQL instance 2 " "
SQL instance 3 " "
This link describes a SQL install:
http://msdn.microsoft.com/en-us/library/ms179530.aspx
One should build a file server to become familiarize with 2008 clustering. 2008 clustering has some AD requirements that 2003 did not have.
Once the cluster is created and the nodes have been added to the cluster, then SQL would be installed (3 times) so each instance of SQL would have a set of shared disk, a network name and an IP address.
Should end up with: Default cluster group with an IP, network name and the quorum drive.
SQL instance 1 group with again IP, network name and SQL data disk(s)
SQL instance 2 " "
SQL instance 3 " "
ASKER
Hi 65td,
Actually I can go with Windows 2003 R2 Ent 64 bit or 2008 R2 Ent 64 bit . Which one is better and stable?
I had a look at documentation link and I don't think I can digest that information. I am not a windows admin by myself , neither we have windows guys here. We are mainly based on RHEL, can do anything under linux.
Do you have a more simple step-by-step blog link or document covering building windows cluster and then sql server cluster?
Thanks
Actually I can go with Windows 2003 R2 Ent 64 bit or 2008 R2 Ent 64 bit . Which one is better and stable?
I had a look at documentation link and I don't think I can digest that information. I am not a windows admin by myself , neither we have windows guys here. We are mainly based on RHEL, can do anything under linux.
Do you have a more simple step-by-step blog link or document covering building windows cluster and then sql server cluster?
Thanks
From an "end of life" prospective one should go for 2008.
2008 does provide more and sometimes confusing features not hard to get use to.
One can also build a 2008 core server (no gui) to host SQL, then the client tools need to be hosted else where.
Is there a windows domain to host the clustered SQL in?
Having said all that, here is a good link to build windows 2008 servers:
http://www.microsoft.com/download/en/details.aspx?id=17157
EOL 2003:
http://support.microsoft.com/lifecycle/?LN=en-ca&x=8&y=6&p1=3198
2008 does provide more and sometimes confusing features not hard to get use to.
One can also build a 2008 core server (no gui) to host SQL, then the client tools need to be hosted else where.
Is there a windows domain to host the clustered SQL in?
Having said all that, here is a good link to build windows 2008 servers:
http://www.microsoft.com/download/en/details.aspx?id=17157
EOL 2003:
http://support.microsoft.com/lifecycle/?LN=en-ca&x=8&y=6&p1=3198
ASKER
Yeap I have a domain controller separately available. The 3 sql server nodes are part of that domain. Oh, they are all on Vmware ESXi.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Hi,
Do you have similar links for vmware workstaion as well? I need to try this on my local machine before going for ESXi main servers
Thanks
Do you have similar links for vmware workstaion as well? I need to try this on my local machine before going for ESXi main servers
Thanks
One group with resources for each instance (resources being shared disk for data and logs, network name and IP address).
Then one should be able to assign a preferred node to each instance, then it should active/active.