Failover clustering vs Sql clustering
- to create a sql cluster do you install sql with the option of creating a cluster and then install the other server with sql on it and install sql to add to that cluster? Or should I use failover clustering?
All Replies
Which version of SQL Server you are talking about?
Thanks!- 2008r2 and 2008 sql
- In your SQL Server Installation Center, Choose "New SQL Server failover cluster installation" and install the first node.
When you are adding the next node, Choose "Add node to a SQL Server failover cluster" in the SQL Server Installation Center
I haven't tried SQL 2008 R2 yet, so not sure about the steps.
Thanks!- Proposed As Answer byJoukoK Friday, February 12, 2010 1:04 PM
Do you have to install failover clustering server 1st before you attempt an install of sql server failover clustering? I read that MSCS has to be configured.
- Hi,
Refer the article http://www.sql-server-performance.com/articles/clustering/cluster_infrastructure_p1.aspx and this https://blogs.msdn.com/blakhani/archive/2007/12/31/how-to-create-sql-20005-cluster-on-virtual-server.aspx
Hemantgiri S. Goswami | http://www.sql-server-citation.com/ | http://www.surat-user-group.org/ -- Surat SQL Server User Group - Im getting this error while trying to install 1st failover node in sql 2008. In my physical failover cluster I get an IP network failure not sure why. I have 1 cable connecting the two servers and also have 1 cable from each server going to my switch.
Error : "Microsoft Cluster Service (MSCS) cluster verification errors" failed. The cluster either has not been verified or there are errors or failures in the verification report. Refer to KB953748 or SQL server books online for more information" - Did you run the Windows Cluster Validation Wizard and it succeded with no errors?
http://technet.microsoft.com/en-us/library/cc732035(WS.10).aspx - No I got a network error on the server failover cluster for ip's. Trying to fix in morning for the heartbeat. I think after that I should be good to go. The error I got is above.
- Yes before start the SQL Cluster installation you need to have the Windows Cluster Installation properly
Trying to configure two nics for a failover cluster from one sever to the other. I know i need to use private ip's for failover cluster.
What type of cable should I use?
and do I need all the setting on the two network cards such as ip,subnet,dns,gateway? They are only connecting to each other to create the heartbeat- I'm not a windows cluster expert , but as far I remember the cluster setup wizard perform many of the configuration for you , you can take a look in http://www.microsoft.com/downloads/details.aspx?FamilyID=518d870c-fa3e-4f6a-97f5-acaf31de6dce&displaylang=en , open the document Step-by-Step Guide for Configuring a Two-Node File Server Failover Cluster in Windows Server 2008.doc , follow the steps just before the File service and with that you will have your windows cluster ready for the Sql installation.
Also in the SQLCAT site there is a comprehensive whitepaper about SQL Server 2008 Clustering including configuration steps and best practices http://sqlcat.com/whitepapers/archive/2009/07/08/sql-server-2008-failover-clustering.aspx Not sure if you still need it or not, but when I was setting up a cluster I found this site with a 4 part article by Edwin Sarmiento, I followed it step by step, and documented the build (had a few things come up outside of his build guide) for my company. This was a great series of articles.
I'm sure you know this by now, but yes you need to build a failover cluster before you build the SQL cluster. you can use regular NIC Cards for the heartbeat.
http://www.mssqltips.com/tip.asp?tip=1687
The configuration of the NICS is not in this guide but some searching online should show you the proper configuration. I realized that I didn't configure the NICs on the 2008 installation so let me pass along some details from my 2003 cluster build guide (i know different version but I hope this helps), and I based this on chapter 8 lesson 1 of the 70-443 Designing a Database Server Infrastructurer Using SQL Server 2005 book.
It recommends that on the PRIVATE NIC
you disable Client for MS Networks and File and Printer Sharing for MS Networks
Select Internet Protocol (TCP/IP) and click properties
specify an ip could be 10.168.20.101 for Node 1 and 10.168.20.102 for Node 2
(these were not IP's that i had to register in DNS, since they are used just for the heartbeat)
subnet mask of 255.255.255.0
do not configure a default gateway or DNS Server
Select the DNS tab and disable Register this connecetion's address in DNS
select WINStab
disable the Enable LMHOSTS Lookup
Again these may be different I hope they help
