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

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

Installing new SQL Failover Cluster Node

Posted By:      Posted Date: October 25, 2010    Points: 0   Category :Sql Server


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?

View Complete Post

More Related Resource Links

Installing an additional SQL Cluster Node



We have a 2 node SQL Failover Cluster (2008).

We wish to replace these 2 Servers (Virtual Machines) with 2 new ones.  I was hoping I could 'cheat' and instead of powering off both current Virtual Machines and then having to do the SQL install from scratch on the 2 new Servers. I could do the following instead:

A:  Add the 2 new Virtual Machines as additional Failover Clusters into the current SQL Environment (so we now have a 4 node SQL Cluster)

B:  Power off the 2 OLD Virtual Machines (so the 2 new Virtual Machines make up the new Cluster)

Would this work or would it be looking for certain files, etc that were installed on the Primary Node?

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

Installing SQL 2008 Failover Node



Can I install SQL on a failover node if SQL is currently online on the Primary Node?  Would this take SQL offline? I am struggling to find a downtime window hence the reason I would like to do this whilst SQL is online on the primary node.

Error Changing Default Backup and Log locations on 2 Node SQL 2008 Failover Cluster


My setup is a SAN providing iSCSI targets for a 2 node SQL 2008 Failover cluster on Windows Server 2008.  With the SAN volumes created, MPIO and iSCSI targets defined on each node, I installed the SQL Server cluster with a single iSCSI target, and therefore assigned database files, log files and backup files to be on that single volume.

I have since added a separate volume for both log files and backup files.  All 3 volumes are online in the SQL Resource Group of the cluster and active on the SQL Server active node of the cluster, and all the volumes are accessible from Windows Explorer on both cluster nodes.

Through SQL Mgmt Studio, I changed the default location of the log files, and I changed the default backup location in the registry for each node.

When I try to create a new database, I get an error saying I do not have permission to access the log file volume.  When I try to restore a database, I get the same error when SQL Mgmt Studio tries to access and display the specified backup volume. The text of the error in each case is:

"Cannot access the specified path or file on the server.  Verify that you have the necessary security privileges and that the path or file exists.

If you know that the services account can access a specified file, type in the full path for the file in the File Name con

Sql failover cluster node 1 install error


After the install I get this error

Cluster resource "Sql server (MSSQLSERVER2) could not be brough online.
The resource failed to come online due to the failure of one or more provider resources. (Exception from HRESULT: 0x80071736)

single node SQL server 2008 R2 failover cluster is down

I install a single node SQL server 2008 R2 failover cluster (server 1) and add a node (server 2) on other server . Now , the first sql server (server 1) is down , server 2 still up so i have 1 server running When i install a new single node sql server cluster on a new server two error occur (failed) : - Microsoft Cluster service (MSCS) cluster verification errors. -Cluster shared disk available check Or can i change the server 2 to the single node sql server clutser to add new node ?

multi-site failover cluster, is node & file share majority quorum really correct in this instance -



The HA design we propose in a nutshell:

Primary site A

Node 1: 1 x physical host for a SQL Failover cluster instance for application A

Node 2: 1 x physical host for a SQL Failover cluster instance for application B

Node 3: 1 x physical host for two SQL Failover cluster instances, one for a test env for application A, and another for a test env for application B

Secondary site B

Node 4: 1 x physical host for a SQL Failover cluster instance that acts as a 3+1 failover node that will pic up the failure of either or all of the 3 nodes in Primary site A.

Now I am a complete novice, but my understanding of quorums are that their purpose is to establish when the cluster must stop running due to things like network failures etc. There really is not much out there in terms of a laymans description for quorums :(

The basic requirement for a multi-site failover cluster with an even number of nodes is to use the node & file share majority configuration, and that is what I have here. 4 x nodes (3 at site A and 1 at site B), and a seperate file share for the witness file (which makes the odd number for a majority).

So my understanding is that:

If node 1 fails, it will failover to node 4

If node 1 and 2 fail, they will both failover to node 4

If node 1, 2 and 3 fail, they will all fail

SQL Server Service does not start on SQL Failover Cluster Node B even though i turn off Node A (acti


We ahev setup a SQL Server (64-bit) Failover Environment which consist of a Node A (active) and Node B (passif).

The setup was completed successfully and was working fine since june 2008.

Our system administrators have reported that, after they made some changes during a maintenance week-end, the SQL Server Services don't start anymore on the node B (even though they turn off the active node A and make Node B as active). Our attempts to manually start those services arealways failing.

Can someone help?

SQL 2008 64 Bit 2 node cluster

I wanted to get some feedback on how much memory and CPUs I needed for each node in a 2 Node Cluster. The operating System will be Windows 2008 R2 64 bit Enterprise and the SQL version will be SQL 2008 R2 64 Bit. It will have a total of 8 instances of SQL Server. 2 of those instances will be SQL Server Reporting Services ( 1 SQL Native and the other SharePoint enabled). This cluster will have both nodes in a virtual enviroment. Any feedback would be greatly appreciated.

Adding second node to SQL Server cluster fails.

I have successfully created a MSCS cluster and I have the SQL cluster up and running on the first node.   When I put the install cd in the second node and go through the install it fails with the error SQL Server Setup has encountered the following error:  Object reference not set to an instance of an object. I'm assuming I get this error because on the cluster node configuration screen the "cluster network name" box is blank.   It won't let me select a name or type a name. The SQL cluster is up and running on the first node.   I can ping the sql cluster network name from both boxes.   The setup shows the installed node and the node I"m trying to add, so I don't see any problem. I have Windows 2008 R2 on both nodes and I'm installing SQL Server 2008 R2.   Any idea how I can get past this error?    Thank you.

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.

Adding thrid Node to SS2K8 cluster fails on adding fileshare

I am attempting to add a third node to a two node cluster. I am using the SS2K8 SP1 slipstream I used to successfully install the other two nodes. The new node of the cluster is:  Hardware: Dell R610 blade  OS: Windows Server 2008 R2 Enterprise 64 bit SQL: SQL Server 2008 SP1 64 bit Enterprise. The two node system has been running for months without problems. How do I fix a failure to add a file share for filestream because the value of group was null (Bold Italics below)? I have not found anything on the web that addresses this problem. Brad The bootstrap summary file woes content(s): Detailed results:   Feature:                       Database Engine Services   Status:                        Failed: see logs for details   MSI status:                    Passed   Configuration status:          Failed: see details below   Configuration error code:      0x11428655   Configuration error description: Value cannot be null.  Parameter name: group &nbs

SQL node remove failed on Cluster :The state of your SQL Server installation was not changed after t

HI guys , Have you faced this .I am not able to remove the SQL Server 2008 ENT node .The error is : Overall summary:   Final result:                  Failed: see details below   Exit code (Decimal):           -2068643838   Exit facility code:            1203   Exit error code:               2   Exit message:                  The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for further details.   Start time:                    2010-09-12 09:40:40   End time:                      2010-09-12 09:48:26   Requested action:              RemoveNode The details.txt shows the same error in a different way : Running Action: CloseUI 2010-09-12 09:44:44 Slp: Stop action skipped in UI

Issues installing SQL 2008 on Win 2008 R2 Cluster

Hello All, I'm having issues installing SQL Server 2008 on a Win 2008 R2 Cluster. The "SQL Server failover cluster install" went fine, now the "Add a node to a SQL Server failover cluster" that is giving me problems. I'm running the setup using slipstream, I was told it would not work without using slipstream. I'm running the command "Setup.exe /PCUSource=D:\sp" inside of the folder where I have the setup file for my Enterprise install of SQL Server 2008. For some reason, the whole install fails, reporting issues with the "Install_sql_engine_core_inst_Cpu64_Action" part of the process. I removed any numbers or characters from the folders my media intallation is located, as this KB below suggests: http://support.microsoft.com/kb/955666 Below is how part of my log file looks like. Let me know if you have any suggestions.   <LOG STARTS> 2010-08-09 14:24:06 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100809_142013\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_ 2010-08-09 14:24:06 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100809_142013\Registry_SOFTWARE_Microsoft_Windows_CurrentVer

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  
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