Install SQL Server 2008 on a Windows Server 2008 Cluster Part 4

By:   |   Comments (41)   |   Related: 1 | 2 | 3 | 4 | > Clustering


Problem

In a previous tip on SQL Server 2008 Installation Process, we have seen how different SQL Server 2008 installation is from its previous versions. Now, we have another challenge to face: installing SQL Server 2008 on a Windows Server 2008 Cluster. Windows Server 2008 has a lot of differences from its previous versions and one of them is the clustering feature. How do I go about building a clustered SQL Server 2008 running on Windows Server 2008?

Solution

To continue this series on Installing SQL Server 2008 on a Windows Server 2008 Cluster, we will look at adding a node in a SQL Server 2008 failover cluster.

  • Part 1 we completed the installation of the Application Server role in both of the servers that we will be using as part of our cluster.
  • Part 2 walked you through the installation of the Failover Cluster Feature, validating the servers that will be a part of the cluster, and creating the cluster.
  • Part 3 completed with a working SQL Server 2008 failover cluster running on a single node.
  • In this tip, we will proceed to add a node in a SQL Server 2008 failover cluster and apply the latest cumulative updates.

Adding a node on a SQL Server 2008 Failover Cluster

Now that you have a working failover cluster, we will make it highly available by adding nodes. The number of nodes you can add in a failover cluster depends on the editions of SQL Server that you will use. A Standard Edition of SQL Server 2008 can support up to two (2) nodes in a failover cluster while the Enterprise Edition supports up to sixteen (16) nodes, which is practically the limit for the Enterprise Edition for Windows Server 2008. As most of the steps in this process are similar to the one when you were installing the failover cluster, I've skipped most of the screenshots.

To add a node on a SQL Server 2008 failover cluster:

  1. Run setup.exe from the installation media to launch SQL Server Installation Center
  2. Click on the Installation link on the left-hand side. Click the Add node to a SQL Server failover cluster link. This will run the SQL Server 2008 Setup wizard.
    There are a couple of glitches when you get to this point. One of them is a popup error with an error message "failed to retrieve data for this request" while in this step. I've seen a Microsoft Connect item on this but refers to CTP6 so I was thinking it has already been resolved. After a few searches and questions asked, SQL Server MVP Geoff Hiten advised that prior to adding another node in the cluster, any cumulative update should be pre-applied to the node before the main installation as the cluster install of the RTM version has some bugs. This creates a patched install script for the RTM installer to use. The fix started with cumulative update 1 so, technically, you can apply any cumulative update. Sounds weird, but it works. You still have to apply the patch after the installation.

    1

  3. In the Setup Support Rules dialog box, validate that the checks return successful results and click OK.
  4. In the Product Key dialog box, enter the product key that came with your installation media and click Next.
    Again, a few glitches on this step. This might seem unusual as you are only being asked about the Product Key. There is also a Microsoft Connect item for this which basically asks you to run the setup.exe in command prompt. There is a popup error with an error message "The current SKU is invalid" while in this step. This usually happens when you use a media with a supplied product key, like the one that comes with an MSDN subscription. What worked for me was to copy the installation media on a local disk, locate the file DefaultSetup.ini file from the installation files and delete it or move it to different location. If you opt to delete the file, make sure you note down the product key written on this file as you will need to manually key this in during the installation process. This forum post will give you quite a few options to solve this issue
  5. In the License Terms dialog box, click the I accept the license terms check box and click Next.
  6. In the Setup Support Rules dialog box, click Install. Validate that the checks return successful results. Again, make sure to fix any errors returned by this check before proceeding with the installation.
  7. In the Cluster Node Configuration dialog box, validate that the information for the existing SQL Server 2008 cluster is correct.

    2

  8. In the Service Accounts dialog box, verify that the information is the same as what you have used to configure the first node.

    3

  9. In the Error and Usage Reporting dialog box, click Next
  10. In the Add Node Rules dialog box, verify that all checks are successful and click Next
  11. In the Ready to Add Node dialog box, verify that all configurations are correct and click Install
  12. In the Complete dialog box, click Close. This concludes adding a node to a SQL Server 2008 Failover Cluster

4

You can validate your cluster installation by expanding the Services and Applications node and check the cluster name of your SQL Server instance. You can now see an option to move the service to another node, in this case, the node you've just added in your failover cluster

5

Applying patches on a SQL Server 2008 cluster

Part of the tasks of a DBA is to apply patches on the database engine and a SQL Server 2008 failover cluster is no exception. In fact, it is not as straight-forward as applying patches and service packs on a stand-alone server. It is important to note that when applying patches or service packs to a SQL Server failover cluster, you should apply them first on the passive node. After completing the installation on the passive node, failover the SQL Server 2008 cluster resource to this node making it the active node. Once the SQL Server service and all other dependencies are up, you can, then, apply the patches on the new passive node. The latest available patch for SQL Server 2008 is cumulative update 4 and is available for request from Microsoft. For more information, check out this Microsoft KB article. You will have to request for the patch from Microsoft as it is not available from the Microsoft Download Center. The screenshots below show cumulative update 3 (version 10.0.1600.22) but the process is basically the same. Also, note that even though you may have already applied the cumulative update due to the bug mentioned above for adding a node in a failover cluster, you still have to apply the patch on both nodes

To apply patches on a SQL Server 2008 failover cluster node:

  1. Run SQLServer2008-KB960484-x86.exe (this would depend on the cumulative update that you want to apply) from the hotfix package you have requested from Microsoft
  2. In the Welcome dialog box, validate that the checks return successful results.

    6

  3. In the License Terms dialog box, click the I accept the license terms check box and click Next

    7

  4. In the Select Features dialog box, validate the SQL Server 2008 components by clicking on the check box. The Upgrade Status field will tell you whether or not the patch has already been applied. Click Next

    8

  5. In the Ready to Update dialog box, verify that all configurations are correct and click Patch

    9

  6. In the Update Progress dialog box, validate that the installation was successful.

    10

  7. In the Complete dialog box, click Close. This concludes patching the passive node of a SQL Server 2008 Failover Cluster

    11

After successfully installing the patch on the passive node, move the SQL Server 2008 cluster resource to this node so it will become the new active node. Make sure that all the SQL Server 2008 cluster dependencies are online prior to applying the patch on the other node. Repeat the process outlined above to the new passive node. A more comprehensive approach for applying a SQL Server 2008 patch to a failover cluster instance is defined in this Microsoft KB article

Congratulations! You now have a working two-node SQL Server 2008 failover cluster running on Windows Server 2008.

Next Steps
  • Download and install an Evaluation copy of Windows Server 2008 and SQL Server 2008 for this tip
  • Review Part 1, Part 2 and Part 3 of this series
  • Start working on building your test environment in preparation for building a SQL Server 2008 cluster on Windows Server 2008


sql server categories

sql server webinars

subscribe to mssqltips

sql server tutorials

sql server white papers

next tip



About the author
MSSQLTips author Edwin Sarmiento Edwin M Sarmiento is a Microsoft SQL Server MVP and Microsoft Certified Master from Ottawa, Canada specializing in high availability, disaster recovery and system infrastructures.

This author pledges the content of this article is based on professional experience and not AI generated.

View all my tips


Comments For This Article




Friday, October 13, 2017 - 3:06:26 PM - Sam Back To Top (67296)

 

 just to follow up about correcting my issue with instance not coming back online it was because I set the CEIP service to local account, but I forgot to do it in the failover node which was causing the resource to come back online during failover. Problem soloved. I did not remove the resouce. 

Friday, October 13, 2017 - 1:45:54 PM - Sam Back To Top (67293)

 

Thanks for your reply, even though I am working on fixing the error. I get CEIP parameter is not set correctly, but I do see that removing the resource is an option as shown by Microsoft, https://support.microsoft.com/en-us/help/3153756/how-to-configure-sql-server-2016-to-send-feedback-to-microsoft

Friday, October 13, 2017 - 11:40:33 AM - bass_player Back To Top (67289)

 

Unfortunately, you cannot remove this service. Refer to this document for additional information on how to deal with the CEIP from within the Failover Cluster Manager. This is as much as I can share with you regarding this. 

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/local-audit-for-sql-server-usage-feedback-collection

Friday, October 13, 2017 - 9:41:16 AM - Sam Back To Top (67279)

 Thanks for your post. I have a question about how you setup the CEIP, i am running into instance failure when try to move it to another resource because of CEIP not coming online. During the installation, I had to change the service account for the CEIP to local service in oder to have the instace coming online. Can this resouce be removed? Please let me know. 

 

Tuesday, December 10, 2013 - 1:03:08 AM - Confused Back To Top (27743)

Well I have been battling to understand why, when at the Account section of the installation of a second node, the system will not accept the password I used to log in. I have been scratching my head - reading every post under the sun all to no avail.

I did notice that some service accounts were given as [email protected] and others were given as DOMAIN\service.instname.instno (the latter being the Win2000 version)

I also noticed comments about strength of password so I thought - I can do that so I changed the password to a much higher strength and RDC in to the server - with new password and thought - best to update the services on the existing node first. I stopped the service, clicked on password and pasted in from the clipboard - (can't go wrong eh?) ha ha says Windows.. Got ya.. it wouldn't accept the password - that I just logged in with. I clicked on browse to select the service account and VOILA! the account name changed to the DOMAIN\user version and readily accepted the password. I then repeated the exercise on the other service. I then found that the node installation would continue (after backing up and forward through the process) to pick up the new name format and accepted the passwords without complaint.

WHY WHY WHY mr/ms Windows?????

I hope my experience saves someone else the pain I went through.

Still Confused

Tuesday, April 30, 2013 - 11:52:37 AM - bass_player Back To Top (23633)

Database backup is no different from your regular backups. For the Windows configuration, having multiple nodes make up for the failure of one node. If, for example, one of the cluster nodes crash, you need to evict that node from the Windows cluster and add a new one. The worst case scenario is that all of the cluster nodes fail at the same time, thus, requiring you to rebuild your cluster. Your documentation will be able to assist you in rebuilding your cluster. However, this is where a DR strategy comes in to make sure that your databases are still up and running while you rebuild your old cluster 

Tuesday, April 30, 2013 - 3:03:07 AM - Manoj Rana Back To Top (23626)

Dear Edwin,

 

Thanks for sharing such valuable information with depth,

I keen to know about back-up and restore portion of cluster configuration on both SQL as well as windows.

 I am waiting for your response,pls update

Thursday, December 13, 2012 - 6:51:35 PM - kiran kumar G Back To Top (20949)

Edwin,

It's very nice & made simple to learn & understand clustering SQL 2008

Thanks Buddy

 

Monday, November 12, 2012 - 11:39:35 AM - bass_player Back To Top (20294)

My installation shows the virtual IP address and port number 1433 on all of the cluster nodes. Do note that you have a 32-bit version and 64-bit version of the SQL Server Network Configuration console so make sure you check the appropriate one

Thursday, November 1, 2012 - 12:00:46 PM - Ronnie Back To Top (20176)

Hi Edwin, everybody,

 

Excellent post. I have stumbled on a gray territory and my question is:

In the SQL Configuration Manager -> Network Configuration section, should I see in the TCP/IP list the IP address used for the instance during the installation? The thing is that I've seen some SQL cluster configurations where the list did NOT contain the IP address but did state the instance PORT.

Did anybody else seen this happening?

Wednesday, September 19, 2012 - 2:07:29 AM - kamal Back To Top (19561)

How to define the passive or Active nodes in Sql Fail over cluster...

Means... When we add the node is it active node or passive node....

Tuesday, July 17, 2012 - 10:36:28 AM - Mohammed Back To Top (18580)

Thanks bass_player for all your valuable information.

I was very usefull.

Monday, July 16, 2012 - 12:58:25 PM - bass_player Back To Top (18545)

What I meant was to install a SQL Server Failover Cluster instance on node 1 twice to create 2 instances. This is no different than a stand-alone server with multiple instances - the number of installations depend on the number of instances. But since we are dealing with a failover cluster, you will run the Add Node option - twice, once per instance - on the other node. Ideally, the process would be to install an instance, add a node and test the failover - your statement is indeed correct. Then, repeat the process. But the flow doesn't really matter if you are doing this pre-production, it just depends on your preferences. As long as you properly test the failover and failback process of all the clustered instances, you should be OK. The ultimate goal is to have a working SQL Server Failover Cluster Instance prior to going live.

Monday, July 16, 2012 - 11:23:11 AM - Mohammed Back To Top (18543)

Hi bass_player,

Very valuable information...

Yes your understanding of my environment is correct. Instance1/2/3/ & 4 are configured to faolover only on Node 5. They cant failover to other nodes in the cluster. They are extended 2 node clusters.

I have a quick question from what you mentioned..just for my knowledge...

" Making all nodes as failover partners require running the Add Node option on all of the nodes in a Windows Failover Cluster. For example, let's say you have a 2-node cluster running 2 instances. To install 2 instances, you will run the installation process twice on node 1. To add the second node, you will run the Add Node process on node 2 "

When you say to install 2 instances, you will run the installation process twice on node 1: i understood that you have to run the new sql server failover cluster installation and add node to a sql failover cluster correct? Or did i miss-understand anything here?

Monday, July 16, 2012 - 9:29:00 AM - bass_player Back To Top (18541)

Correct me if I'm wrong but from your description, it seems that you have an extended 2-node cluster. This means that Instance1/2/3/4 is configured to only failover on Node 5 and not on the other nodes in the cluster. Instance1 cannot failover on Node2/3/4 and same as the other instances. Is my understanding of your environment correct? The reason I came up with this description is because when you run the Add Node option during the installation, you have the option to select the instance name on which to add the cluster node. Making all nodes as failover partners require running the Add Node option on all of the nodes in a Windows Failover Cluster. For example, let's say you have a 2-node cluster running 2 instances. To install 2 instances, you will run the installation process twice on node 1. To add the second node, you will run the Add Node process on node 2. All-in-all, you ran the setup 4 times. Imagine doing this for a 3-node, 3 instance cluster. The installation process will be 9 times if you intend to use all 3 nodes as failover partners. That was why I assumed that, in your environment, 4 instance in 5 modes would take 20 times the installation. If this is not how your cluster is configured, just treat each instance as an extended 2-node SQL Server Failover Cluster instance and apply the process you've outlined 

Sunday, July 15, 2012 - 10:37:34 PM - Mohammed Back To Top (18533)

Thanks Bass_player for the response...

I am little bit confused what you meant by 20 times.

I currently have the below plan. As mentioned, mine is a A/A/A/A/P cluster.So basically my node 1,2,3 and 4 are active with running instances and node 5 is passive without any running instance.

  1. I will first install Service pack on Node 5 which is passive and doesn't have any instance running on it.At this point Node 5 is up upgraded. I dont need to upgrade it again.
  2. Now i will failover Instance1 from node1 to node 5. Now node 1 becomes passive and i will upgrade node 1. Once the upgrade is done i will failover Instance1 from node 5 back to node 1 where it was running initially. Node 5 is back to passive now.
  3. Now i will failover Instance2 from node2 to node 5. Now node 2 becomes passive and i will upgrade node 2. Once the upgrade is done i will failover Instance2 from node 5 back to node 2 where it was running initially. Node 5 is back to passive now.
  4. Now i will failover Instance3 from node3 to node 5. Now node 3 becomes passive and i will upgrade node 3. Once the upgrade is done i will failover Instance3 from node 5 back to node 3 where it was running initially. Node 5 is back to passive now.
  5. Now i will failover Instance4 from node4 to node 5. Now node 4 becomes passive and i will upgrade node 4. Once the upgrade is done i will failover Instance4 from node 5 back to node 4 where it was running initially. Node 5 is back to passive now.

So the whole cluster is upgraded now on all the nodes are with the same service pack level. Let me know if this makes sense.

FYI..i have upgraded clusters many times before but that was only 2 Node A/P cluster. I use to first upgrade Passive node2 and then failover Active Node1 to Passive and upgrade the Node 1. This was very straight forward. I guess the same applies for a 4 active and 1 passive cluster.The whole concept is, applying rolling upgrade i.e when ever you are upgrading a node it is recommended to not have SQL instance running on it. This was we can decrease the down time.\

Let me know your thoughts.

Thanks,

Sunday, July 15, 2012 - 8:15:22 PM - bass_player Back To Top (18531)

The key to applying service packs is to always patch the node that does not host the SQL Server instance. I'm guessing this is a 5-node, multiple instance cluster with one node acting as a standby. In this case, start installing the service pack on the 5th node. After installing the service pack, failover one of the instances to this node and install the service pack on the node from which the instance came from. Repeat the process. You will have to repeat this process 20 times - once per instance per node (on a 5-node, 4-instance cluster)

Sunday, July 15, 2012 - 6:42:47 PM - Mohammed Back To Top (18530)

Hello Edwin,

Thanks Very much for the article. I have followed the steps as you mentioned and everything went fine without any issues.

I have a question regarding installing the service packs in a A/A/A/A/P cluster. This is SQL 2008 R2 in a Win 2008 cluster. I have installed patches and Service packs in a A/P cluster but this is the first time i am installing in a A/A/A/A/P cluster. Any help will be greatly appreciated.

Thanks,

Mohammed

Wednesday, June 13, 2012 - 7:32:27 PM - LightheartAl Back To Top (17977)

I'm preparing my first SQL cluster install; a SQL2K8 (Ent) R2 SP1 on a Win 2K (Ent) R2 SP1 2-node cluster. 

First I wanted to ask if it's possible to install the RTM, followed by the SP1, on one node before doing the AddNode and then the upgrade as you describe here.

Second, this will be an active-active cluster (i.e. Operations will be primary on Node1, Warehouse primary on Node2).  I'm thinking that it would be best to install/create all instances on Node1, then AddNode, and then re-host/failover the Warehouse instance to Node2. 

Your thoughts?

Thanks,

Al

Friday, February 17, 2012 - 2:51:04 PM - max Back To Top (16061)
No, you don't have to reboot the nodes, but if you have to patch it (wupdate/wsus) it may happend.

Friday, February 17, 2012 - 12:35:30 PM - Chaitanya Back To Top (16054)
Hi, We are going to instal the sql server 2k8r2 on 2k8 cluster. the cluster is a active active cluster and n1 have 2 instance and n2 have 2 instance. now we are going to instal the another instance. Is it requeried to reboot the server after instal the new instance? Thank You, Chaitanya.

Tuesday, May 17, 2011 - 3:43:07 PM - bass_player Back To Top (13855)

Adding a database to the new cluster is nothing different from adding a new one from a non-clustered instance. Once you're inside SQL Server, there's really no difference between a clustered instance and a non-clustered one

Tuesday, May 17, 2011 - 3:02:35 PM - Johnathon Back To Top (13854)

I finally got it working.. What I did wrong was I forgot to add storage on the failover cluster...

I have seen that article tho..

Another question, How do you add a database to the new cluster?

Tuesday, May 17, 2011 - 2:47:44 PM - bass_player Back To Top (13853)

Have you seen this?

http://www.sysprobs.com/nas-vmware-workstation-iscsi-target

Tuesday, May 17, 2011 - 1:16:48 PM - Johnathon Back To Top (13852)

I followed your steps to the letter but everytime the sql server setup support rules go throught it tells me that the Cluster shared disk availability check failed.

 

I am on Vmware with 2 windows server 2008

using freenas for the storage

could you help me out?

Tuesday, February 8, 2011 - 4:29:18 PM - Ven Back To Top (12880)

Edwin,

 

You did a great job. Thank you so much one of the best post I've ever seen.  Very useful article.

Tuesday, February 1, 2011 - 5:44:26 PM - bass_player Back To Top (12778)

Hi max,

Installing another instance on an existing cluster is dependent on the load that you want to run on that instance and the existing load on the current clustered instance. Other requirements are just for separation of applications like security, administration, etc. Before installing an additional instance on an existing server - clustered or not - note down the reasons why you would do so  

Tuesday, February 1, 2011 - 4:09:23 PM - Rob Back To Top (12777)

Thanks for the very clear instructions! I've had problems setting up my SQL cluster for two weeks, and this is the first tutorial I've come across that explains correctly and in detail the required steps for setting up a cluster. Thanks!

Wednesday, January 19, 2011 - 1:16:06 AM - max Back To Top (12636)

Hi,

can you help my in this task?

Do i need to install another cluster or only another instance and choose preferred owner as node2?

thanks in advance for any help

regards

Max

Wednesday, January 5, 2011 - 11:57:21 PM - bass_player Back To Top (12501)

Hi Max,

This is a great idea for a tip. I'll work on this tip for this month

Tuesday, January 4, 2011 - 7:32:03 AM - max Back To Top (12483)

Hallo,

 it's possible to add a second (named) instance to the failover cluster and bring it active over the first-instance passive node?

If it's possible, where should i start? add new failover cluster?

thanks

regards

MB

Thursday, November 11, 2010 - 7:36:24 PM - Moonshdw8 Back To Top (10358)

THANK YOU!! THANK YOU!! THANK YOU!! I spent weeks scouring the net following tidbits and pieces of this installation process and when I finally stumbled upon this gem that actually shows and explains each step of the process (rather than skimming over huge parts like Microsoft does) I was on my knees thanking god.

Thanks so much for creating this. Great Tutorial! I only wish I found it weeks ago.

Friday, January 15, 2010 - 2:49:26 AM - SBracco Back To Top (4721)

 Ok, if you are working with VMWare is another story, if I'm not wrong, there are some configurations which are not supported, but there are some of them which should work anyway.

Now you say that  the executables are not on the secondary node, which means that something is missing,. if you copy, not all is done, as the installation is also creating some registry.

I suppose that the cluster (as you say) is failing on second node, there is an installation log and you couls start from there, but my firste suggestion is to open the registry and to check if you have on the second node:

 

HKELY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSSQL10.%INSTANCE_NAME%\Cluster

 

Under this root you should have the cluster name under ClusterName

 

At set-up, it is the registry which is driving the system to see the service correctly as a Cluster, if you do not have the entry, the Cluster is not recognized, and something in the previous part os the SQL Server Node Add Procedure, failed.

 

Let us know the result.

 

Stefano

 

Thursday, January 14, 2010 - 1:58:01 PM - v2k2m Back To Top (4718)
Thanks for the reply. I did the installation 3 times and every time I faced the same issue. I even installed the SQL server with drives failed over to the second node and this time the cluster could recongnize the SQL server service since it installed it on the local C:\ drive and the common files on the shared drive but created new folders. I verified that by creating the new files and folders and then tried to failback and surprisingly those files and folders were not there on the (first node) active node. I am using Windows 2008 enterprise plain, no R2 and SQL 2008 enterprise. I manually removed the SQL Agent service and deleted it, but no luck. Created new one which doesn't want to work. This whole problem is only on the passive node. The active node is ok and can start all the services and agent service without any problem. There is something with the installation program that is not right or it might be that the installation which I am performing is not compatible with VMWare but I doubt that since I can failover other services like MSDTC on both nodes without any issue. It is this SQL setup is not working for the 2nd node. Any help is appreciated.

Thursday, January 14, 2010 - 12:49:13 PM - SBracco Back To Top (4717)
Very strange, I had the same problem last week installing a Cluster, and I noticed that you can add the SQL Server + SQL Agent by hand after the installation, you can try, but there is something wrong in the installation process. Anyway, the normal behavior is that the SQL Server and Agent can be moved and activates transparently to the second node and the shared drives are mounted to the second node. Don't know what version you are installing, but for shared drives we had some problems, and I managed to keep them off-line during installation, then MS Cluster is taking care to activate them (and set them to "Reserved") as needed. The installation procedure should do all this work, my suggestion is to remove and re-install everything. In this way it should create the Agent and SQL Server transparently and without any error. HTH. Stefano

Thursday, January 14, 2010 - 12:26:52 PM - v2k2m Back To Top (4715)
When you install the second node do you need to failover the common drive/s to the second node. what I mean to say is do we need to make the second node as primary or not? I tried the install on the second node and it didnt write anything in the shared drive. I am wondering what happened there since I kept the first node as active during the install. Now when I try to failover it just can't enable the SQL server and SQL Server agent service. Any thoughts.... Appreciate your help.

Thursday, October 29, 2009 - 3:30:38 PM - bass_player Back To Top (4336)

This is supported. The only thing that you would have to worry about is your hardware. You can install as many instance as you possibly can in a node and use the other nodes as passive nodes. But, then, you will have to worry about administration - both from the Windows side and the SQL Server side.

Wednesday, October 28, 2009 - 1:21:49 PM - SBracco Back To Top (4327)

I have an additional question.

If I want to have 2 instances on 2 nodes, is this supported as in SQL Server 2005?

Is it enough I put the second instance on Node 2 as describided in part 3?

 

Many thanks for the hints!

 

Stefano

 

Thursday, April 9, 2009 - 5:25:31 PM - aaditya2000 Back To Top (3158)

Hello:

 So should i understand that i have to do this "failover cluster installation on the first node and run the Add node on the other nodes" on each nodes. where i have 4 nodes cluster, quorum configured as nodes & disk majority.(Witness Disk)

Thanks

Wednesday, April 8, 2009 - 4:11:08 PM - bass_player Back To Top (3151)

You just run the failover cluster installation on the first node and run the Add node on the other nodes.  You definitely need to run the setup.exe on all nodes as this fires up the installer where you can select either of the options


Thursday, April 2, 2009 - 11:21:20 AM - aaditya2000 Back To Top (3120)

Hello:

 I have 4 node cluster (even Node) with Node & Disk Majority (Witness DISK).

My question is in reference to SQL installation.

Do i have to run SQL setup.exe on each individual NODE & then finally add nodes as you mentioned in PART - 4.

 Any pointer is appreciated.

 Thanks














get free sql tips
agree to terms