SQL Server Performance Forum – Threads Archive

Setup 1/2 node

Hi all,
Is it possible to install sql 2000 on a 2 node a/p setup the following way??? – install os and cluster on 1st node
– install sql 2000 and sp4 (as cluster) on 1st node
– install user db’s
– work a short time with this one node cluster setup – install os on 2nd node
– add 2nd node to cluster
– start sql 2000 setup to add 2nd node into sql cluster
– install sp4 again to have both nodes uptodate Have anybody done this already? I tried it a while ago but was unable to reaply sp4 the second time (last step, can’t remember the exact error) Thx for your hints
acki

---

Yes, it is possible…
Check BOL topic "failover clustered instance of SQL Server/as standalone instance"
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

---

MohammedU
I know it should be possible from the BOL but in my test it wasn’t 🙁
That’s why I’m asking if someone did this scenario already. In other words:
– I have a one node sql 2000 cluster setup with sp4 up and running. -> OK
– I was able to add the second node through sqlsetup/maintain cluster. -> OK
– I was not able to proberly reaply sp4 on the now two node cluster.
(SP4 setup went through without errormessage but did not show dialog with "update ms search and apply sp4". See this thread for resulting error:http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=21357) For my understanding one node (the existing one) is with sp4 the 2nd node (the new one) is without any sp (or sp1 by default? ) To me it looks that sp4 wasn’t installed on 2nd node at all. Questions:
– Is it even nescessary to reaply sp4 or does newly added node get’s sp4 binaries from 1st node ?
– How to reaply sp4?
Any hint?
acki

---

Service pack is based on the instance not based on cluster. You have to install the SP4 on the new node after adding to the cluster. When you install the service pack it should update the binaries on the other node related to this instance. To make you got the correct service pack run the SELECT @@Version on node then failover to the other node then run SELECT @@Version to make sure it gives the same buil when sql runs on both nodes. MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

---

MohammedU
The problem is I cannot failover and therefore not check what’s installed on second node. TIA
acki

---

Is there is problem with failover to other node..
or businees reasons? You can check the sqlservr.exe file version in the binn folder…
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

---

MohammendU
I reactivate this thread again.
I have db’s on a one node cluster setup running with sp4.
Adding the second node works, but reaplying service pack does not. If I reaply service pack with existing sp4 node as active node there is no dialog "update ms search an aply sp4" I cannot failover to new added node because of different sp level (failover fails back to existing sp4 node) I cannot install sp4 on inactive node. How to work around this?
TIA
acki

---

.. but reapplying SP doesn’t…
Why, any error or warnings if you have attempted to failover to this node?
I would suggest to refer to README of SP4 too. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.

---

satya,
I guess sp4 changes system db’s that’s why failover to a node without sp4 binaries fails. SP4 shows no error but the strange thing is that during sp4 the dialog "upgrade ms-serach and install sp4" is missing.
My point of view is that sp4 checks that it is already installed on node and does not care about other nodes and therefore will not apply again. acki

---

Have you reattempted to install SP4 again?
If you have similar versions of service pack between the nodes then the failover will work, as you said master database & SQL binaries are the key here. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.

---

satya,
That’s exactly my problem. I have one node on sp4 (active) and one node unpatched.
SP4 recognizes the patched system and therefore does not reaply and a failover
does not work because of incompatible system db’s.
Reaplying sp4 again (3rd time) does not help -> again missing dialog acki

---

How about evicting that node and reattach again as in order to have a functional cluster, you must have some kind of shared storage which is accessible by both servers.
Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.

---

If you have one node without SP and one node with SP4 should not cuase the failover problem because binaries and system databases are totally seperate for each node…
only common/shared files are the same… When you try to failover to another node what error do you get? Did you check the SQL error log, application/system log (Event viewer) and cluster log for errors related to this?
MohammedU.
Microsoft SQL Server MVP
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

---

I do not agree, binaries are seperated but not system databases!!!
For my understandig system db’s are placed on clustered disk and therefore the same for all nodes. Do I missunderstand somthing fundamental here? Cannot check any errorlogs anymore. Had to rebuild hole cluster do go on with my installation.
Just tried to find a solution for future workarounds. acki

---

If you have to different instance on two node cluster you will have two set of system databases independent to each other… When you failover your same system databases move to different node…so if your system dbs have build sp4 then they will be the same with sp4…system databases build will not change… MohammedU.
Microsoft SQL Server MVP
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

---

MohammedU
I have only one (default) instance (a/p setup), means one set of system db’s on a shared cluster disk.
Scenario after adding 2nd node is then one node with binaries and system dbs on sp4 level (existing node), other node (newly added node) binaries from original setup (guess it’s sp1).
Therefore failover will NOT work because system db’s from sp4 node are not compatible to binaries on new node. But that’s not the point, the point is I cannot reaply sp4 from the existing sp4 node 🙁 acki

---

When you failover the SP4 node to other node they will not use the same binaries…
Binaries are installed for each node…only few common/shared files are used by both nodes where BINN folder is different for each node…
MohammedU.
Microsoft SQL Server MVP
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

---

When you add the second node, SP4 should be reapplied to that node if I remember correctly. At least thats how the rebuild master tool works, it will reapply sp4 after you rebuild master. I would assume adding nodes to a cluster works the same way. Now if it doesn’t work that way you can still apply SP4 again. You mention "If I reaply service pack with existing sp4 node as active node there is no dialog "update ms search an aply sp4". This doesnt matter, its just the ms search service that wont be upgraded again. It’s a seperate service on the node. Just continue with the SP4 setup. If that doesnt work, post the sql, cluster and event log errors you get when the failover fails.

---

]]>