.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Migrate existing instances to failover cluster

Posted By:      Posted Date: April 10, 2011    Points: 0   Category :

I am a newbie. I read the following from on the page http://msdn.microsoft.com/en-us/library/ms179410.aspx 

Migration of existing instances of SQL Server to a failover cluster

First, you must collect current baselines for the existing servers, noting any existing bottlenecks. Assuming baseline performance statistics provide the following needs, and that a single drive with mount points would cover drive requirements, that would leave you with the following configuration:

SQL Server 1 - 8 processors, 16 GB of RAM
SQL Server 2 - 4 processors, 8 GB of RAM (needs RAM, plan for 12 GB)
SQL Server 3 – 2 processors, 16GB of RAM (baseline shows need for additional processors)
SQL Server 4 – 4 processors, 8 GB of RAM (needs additional network bandwidth, add network adapters for 4 dedicated connections)

To replace these four servers, the cluster node would require the following minimum configuration:
18 processors, 54 GB of RAM, and 6 network adapters 

I have the following questions.

* What is the meaning of "to replace these four servers"?

View Complete Post

More Related Resource Links

Installing SQL Cluster side-by-side with existing instances


Hi All,

 I have two servers with SQL 2005 running as separate instances. I now want to install a cluster over the two boxes with SQL Server 2008R2 while keeping the 2005 instances running for a while. The databases will then be migrated over from the 2005 instances to the cluster for testing. After a test period, the 2005 instances will have a final migration and be decommissioned.

So for server001, server002 and SQL Cluster name SQLCLU001, I should be able to reference them all on the network individually after installation and the individual instances will continue to run on the local disk until decommissioned IIRC.

From what i've done before, I think this should be fine and shouldn't throw any issues but I wanted to check that there weren't any obvious blockers to this. Licenses are all ok, servers are fast enough to cope with the new configuration. It's just the process I wanted to check out as i've not done an upgrade in quite this way before


Network failure in Cluster Environment,will it stop the SQL Server Instances?

Hi All I have problem with cluster Environment that is there is network failure in Cluster Environment,will it stop SQL Server Instances Event viewrer Information 6:22:09 The MSSQLSERVER service entered the stopped state. 6:22:05 The MSSQLSERVER service was successfully sent a stop control. 6:22:04 The SQLSERVERAGENT service entered the stopped state. 6:21:43 The node lost communication with cluster node 'MSSQL0002' on network 'LAN'. 6:22:02 The SQLSERVERAGENT service was successfully sent a stop control. 6:22:02 Cluster resource 'SQL IP Address1(SQLCLUSTER)' in Resource Group 'SQL' failed. 6:22:02 The TCP/IP interface for Cluster IP Address 'Cluster IP Address' has failed. 6:22:02 The TCP/IP interface for Cluster IP Address 'Cluster IP Address' has failed. 6:22:02 The TCP/IP interface for Cluster IP Address 'MSDTC IP address' has failed. 6:22:02 The TCP/IP interface for Cluster IP Address 'MSDTC IP address' has failed. 6:22:02 The TCP/IP interface for Cluster IP Address 'SQL IP Address1(SQLCLUSTER)' has failed. 6:21:58 The TCP/IP interface for Cluster IP Address 'SQL IP Address1(SQLCLUSTER)' has failed. 6:21:58 Cluster network 'LAN' is operational (up). All available server cluster nodes attached to the network can communicate using it. 6:21:58 The interface for cluster node 'MSSQL0002' on network 'LAN' failed. If the condition persist

SQL server 2008 failover cluster install

Hello all, Looking for the definitive answer with supporting documentation (link). Does a SQL server 2008 cluster have to be installed as or run as a domain service account or can local accounts be used?  I looked for a document that stated yes or no and could not find one. If anyone can provide info it would be much appreciated. Have all ready looked at these 2 links of interest. http://msdn.microsoft.com/en-us/library/ms143504.aspx#Service_SID http://technet.microsoft.com/en-us/library/cc731002(WS.10).aspx Thanks in advance,  

why would a dba do a manual failover on a cluster

Why would a dba do manual failover because of high cpu?  I got no answer from dba, but cpu did improve from 85 to 60, then down to about 40%.  My thought is there was parameter sniffing problem and clear proc cache from failover fixed the problem, recompiling all the procs is why cpu high at first after failover?  Until cpp started spiking to 80 it was under 50% all day.

Issues with Kerberos and SQL Server failover-cluster

I have a dual-instance SQL 2008 SP1 2-node Failover-cluster running on Server 2008 x64 SP2. SPNs have been manually created in AD for the service account running SQL Server (on both nodes).When the cluster nodes first boot up and the virtual groups come online, everything works flawlessly. I have linked server connections set up between the two instances of SQL server, with one instance running on each node. I can successfully make linked server connections from one instance to another from a third client PC, indicating Kerberos is working successfully, which is great!Problem is, this all stops working as soon as one of the SQL cluster groups fails over (or is taken offline, and moved to the other node). As soon as this happens, all authentications seems to fall back to NTLM. Of course, running both instances on the same physical node will work since Kerberos is not required for this. But as soon as an instance moves to another node - kerberos seems to be permenantly broken for that instance, even if moved back to its original node, until both nodes are rebooted again.One thing to note - the service account running SQL server is not a domain admin. This of course prevents SQL server from auto-registering the SPN upon startup and generates the following in the SQL log: "The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL

The SQL Server failover cluster instance name 'Server02' already exists as a clustered resource. S

Hello, I have a node of 2 servers of Win 2008 R2 Enterprise and trying to install a 2nd instance in a SQL 2008 R2 Cluster. I had SQL_INSTANCE2 previously installed that I removed from the two nodes. Now when I attempt to install it again from scratch, in setup GUI where I specify the SQL Server Network Name and enter the previously entered name "Server02", I get a failure in the setup with the following error message: "The SQL Server failover cluster instance name 'Server02' already exists as a clustered resource. Specify a different failover cluster instance name." How do I fix this problem, I don't want to enter a new name like "Server03" in order to proceed with the setup, because when I do enter "Server03" the setup does continue without an error message. So what am I missing? Do I have to ask the DNS administrator to see if there's an A record for "Server03" and have him delete it so that the setup works? Or the fix is by doing something else? I would appreciate any help. Thank you  

[amateur question] Why can't I use MSCS cluster ip address for SQL 2008 failover cluster?

Good day! Recently, I was tasked to set up SQL 2008 failover cluster on both Windows 2003 Server (Enterprise ed). Everything was set up perfectly, failover work on both cluster nodes. Now the question is my boss asked me a very basic question on which I'm unable to give him a detailed explanation on why can't used only a single IP Address for both MSCS cluster and SQL failover cluster? I replied back him (amateurish) its because of the requirement stated on SQL 2008 failover cluster. I can't even be allowed to install when I keyed in the already used IP Address for MSCS. Can any folks enlighten me on these? Best Regards

SQL server 2008R2 install on a server 2008 R2 failover cluster. Other resources won't failover to o

As the subject says, I've built a fresh install w2k8r2 and sql2k8r2 failover cluster. Sql works fine on the primary node, but when I test a failover it breaks. Specifically, if I were to stop the node1 cluster service (causing the cluster to switch to node2), windows changes the cluster DNS appropriatly and moves the shared storage just fine, but sql server doesn't failover.  Server Name, Disk Drives and Other Resources all go offline. I've verified that the advanced policies of the server name, IP, cluster drives all have both nodes checked as possible owners However, Other resources only lists node1 as a possible owner and there appears to be no way to add node2.  Under the Other resources, SQL Server and SQL Server Agent are listed. I'm sorta stumped, I've been combing the forums and have found similar issues, but nothing seems to explain why the two resources won't failover.

SQL Server 2005 Cluster failover issue

Hi All, I'm fequently experience Cluster failover issue. The cluster tries to failover and it fails back. Because of this the SQL server is getting restarted and this is a bugging issue during business hours. The following are the System event logs, Cluster resource 'SQL Server' in Resource Group 'Production' failed. The SQL Server Agent (MSSQLSERVER) service was successfully sent a stop control. The SQL Server Agent (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a stop control. The SQL Server (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a start control. The SQL Server (MSSQLSERVER) service entered the running state. The Cluster Service brought the Resource Group "Production" online.    The following are the application event logs, The client was unable to reuse a session with SPID 131, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Query timeout expired [sqsrvres] OnlineThread: QP is not online. The client was unable

Multiple Sql instances in a cluster



I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx

that this is not recommended. Does anyone know why this is or what problems I may encounter?

Its is running Sql 2005 on a 64 bit windows Server 2003.

Installing Integration services as standalone on a existing cluster


Hi All,

  I have SQL Server 2005 std edition installed on a windows 2003 clustered server. As integration services does not support i was asked to install it as a standalone on both nodes. When I had started the setup it showing on both the nodes. How do i install it only one node at a time and not on the cluster. Do i need to have separate instance of sql server too.



Chandra Mohan



Intermittent unavailability of an instance in a failover cluster while a standby node is offline.


Hi everyone.

I've got a small failover cluster that I run for the websites my company has. During a RAM upgrade of the standby server, our websites started to show errors about not being able to access the database server. I verified that the instance was indeed up and the server accessable via remote desktop.
I also tried a SQL connection to it and it worked, but that might have been after it became available again.

This happened on and off until we were able to roll back the hardware changes that were in progress on the standby server and we were able to bring it back up.

There was nothing of interest in the SQL Server log, but there is a continous log for the whole duration of the problem, so there was no restart of the SQL Server service. The event viewer is of more interest, since it shows events relating to the heartbeat network card, but I don't know how that would affect the availability of the server, since the standby node is offline. I'd appreciate any help you can provide, it's not very redundant if it also depends on the standby server being up. :)

Here are the event logs from the time of the problem:

Level Date and Time Source Event ID Task Category
Information 4/23/2010 10:55:56 AM Microsoft-Wind

SQL Server 2008 A/P Cluster Does not Failover



I have a SQL Server 2008 Enterprise Edition A/P cluster Server on Windows 2008. Recently One of the Clustered Disks Went OFFLINE. The SQL Resource which has Dependency on the clustered Disk also went offline. Shouldnt a Failover of the resources be happening to the second node, if there is a failure in the first node? Are there any settings which need to altered?




Hi, I have successfully installed the slip stream SQL SERVER 2008 Enterprise  sp1  on the two node fail over cluster.Now i need to implement the 2 node failover cluster installation again with the standard  edition of SQL SERVER 2008 sp1.

My question is do i  need to go for a slipstream installation with  standard edition also?

Failover Cluster Install on Server 2008 R2 (RC)

Has anyone successfully installed a SQL Server 2008 Failover Cluster on Server 2008 R2 (RC)? I'm getting stuck at the Instance Configuration screen, i get an error when trying to detect the SQL Server Network Name, here is the error:

The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'

I've setup a 2008 SQL Failover Cluster in Server 2008 SP1 without a problem.

Installing new SQL Failover Cluster Node



I have a 2 Node SQL Cluster.  Node A is the Primary Box where SQL was first installed and Node B is the Secondary Box where I added it to the Failover Cluster.

I now wish to replace Node A with a new Server (reason being, we have had issues with this and wish to rebuild it from scratch).  My question is...

If I move the SQL Resources onto Node B, can I then rebuild Node A Server and then add it as 'failover cluster node'?  Or will this not work as it will already detect that Node A was part of this Cluster before? And during the initial install did Node A install files that are required for Node B to work?

Failover Cluster - What if DC goes down?


Hi Everyone,

We are about to install our first SQL Server failover cluster and I'm having a pickle trying to find the answer to this question. I know that there should be redundancy on the domain controller and active directory. But what exactly happens if the DC or AD goes down and the backup doesn't come up? This would strickly be Windows Server 2008 R2 Enterprise Edition running SQL Server 2008 R2 Enterprise Edition using a local adminsitrator account for the cluster service on each node. My guess is either the cluster becomes completely unavailable or the cluster remains avaiable but no longer has the ability to failover. Thanks in advance for your time.


ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend