Hi!
I have a problem with a 4-node cluster. It was a 2-node sql2k on w2k.
We installed new hw with w2k3 and installed the old instances there
(restore). After that we added 2 more w2k3 nodes and installed the
original 2 instances on all 4 nodes. We also set up 2 new instances to
be a total of 4.
The problem is that when we put in the new hw (node 3 and 4) we saw
that we lost the control of the fulltext resource on the first 2
instances. It started failing and then failback, sometimes it started,
sometimes not. This started before we actually joined node 3-4 to the
clustrer. Since we don't use fulltext we took away the resource from
the cluster on these 2 instances. On the new instances (3 and 4) there
has newer been a problem. All nodes can run all 4 instances. There is
no problem with any other resource.
I have seen kb 812666 and I think that I should try rebuildning
fulltext. I think it looks very complex, is there anyone that have
done this?
/Peter
Peter,
Yes, KB article 812666 "How to recover a failed full-text search resource on
a clustered instance of SQL Server 2000" at
http://support.microsoft.com/default.aspx?kbid=812666 is complex, but since
you don't use the MSSearch (Fulltext ) service, and have already removed the
fulltext (Microsoft Search) service from the cluster resource, rebuilding
this service is not necessary/
Note, you can also post FTS related questions to the newsgroup:
microsoft.public.sqlserver.fulltext
Regards,
John
"Peter Lindberg" <peter.lindbergTAKE@.AWAYmartinsson.se> wrote in message
news:415bfda4.4507871@.msnews.microsoft.com...
> Hi!
> I have a problem with a 4-node cluster. It was a 2-node sql2k on w2k.
> We installed new hw with w2k3 and installed the old instances there
> (restore). After that we added 2 more w2k3 nodes and installed the
> original 2 instances on all 4 nodes. We also set up 2 new instances to
> be a total of 4.
> The problem is that when we put in the new hw (node 3 and 4) we saw
> that we lost the control of the fulltext resource on the first 2
> instances. It started failing and then failback, sometimes it started,
> sometimes not. This started before we actually joined node 3-4 to the
> clustrer. Since we don't use fulltext we took away the resource from
> the cluster on these 2 instances. On the new instances (3 and 4) there
> has newer been a problem. All nodes can run all 4 instances. There is
> no problem with any other resource.
> I have seen kb 812666 and I think that I should try rebuildning
> fulltext. I think it looks very complex, is there anyone that have
> done this?
> /Peter
|||John,
thanks for the reply. My intention is to get all 4 nodes equal setup.
We want to be able to run new databases where it's best suitet and
don't depend on differenses between instances. That's way I want to do
this. I have to set up my test environment so I can test it before I
go in the production.
Have you done this in a cluster?
/Peter
On Thu, 30 Sep 2004 11:19:01 -0700, "John Kane" <jt-kane@.comcast.net>
wrotc:
>Peter,
>Yes, KB article 812666 "How to recover a failed full-text search resource on
>a clustered instance of SQL Server 2000" at
>http://support.microsoft.com/default.aspx?kbid=812666 is complex, but since
>you don't use the MSSearch (Fulltext ) service, and have already removed the
>fulltext (Microsoft Search) service from the cluster resource, rebuilding
>this service is not necessary/
>Note, you can also post FTS related questions to the newsgroup:
>microsoft.public.sqlserver.fulltext
>Regards,
>John
>
>
>"Peter Lindberg" <peter.lindbergTAKE@.AWAYmartinsson.se> wrote in message
>news:415bfda4.4507871@.msnews.microsoft.com...
>
|||You're welcome, Peter,
Unfortunately, I do not have a clustered environment to test this KB
article, as I have only one home server and a laptop... ;-(
If you do have a test clustered environment, even one with just two nodes,
I'd recommend that you test using that environment.
Regards,
John
"Peter Lindberg" <peter.lindbergTAKE@.AWAYmartinsson.se> wrote in message
news:415d70eb.31078308@.msnews.microsoft.com...[vbcol=seagreen]
> John,
> thanks for the reply. My intention is to get all 4 nodes equal setup.
> We want to be able to run new databases where it's best suitet and
> don't depend on differenses between instances. That's way I want to do
> this. I have to set up my test environment so I can test it before I
> go in the production.
> Have you done this in a cluster?
> /Peter
> On Thu, 30 Sep 2004 11:19:01 -0700, "John Kane" <jt-kane@.comcast.net>
> wrotc:
on[vbcol=seagreen]
since[vbcol=seagreen]
the
>
|||I'll definitive test it. It will be under vmware gsx.
/Peter
On Mon, 4 Oct 2004 10:57:02 -0700, "John Kane" <jt-kane@.comcast.net>
wrotc:
>You're welcome, Peter,
>Unfortunately, I do not have a clustered environment to test this KB
>article, as I have only one home server and a laptop... ;-(
>If you do have a test clustered environment, even one with just two nodes,
>I'd recommend that you test using that environment.
>Regards,
>John
>
>"Peter Lindberg" <peter.lindbergTAKE@.AWAYmartinsson.se> wrote in message
>news:415d70eb.31078308@.msnews.microsoft.com...
>on
>since
>the
>
Showing posts with label 2-node. Show all posts
Showing posts with label 2-node. Show all posts
Tuesday, March 20, 2012
Monday, March 12, 2012
Reboot SAN of SQL Cluster
We are planning a recycle of our SAN to which our active/passive 2-node SQL
cluster is attached. Is there anything special to be aware of?
We will do the following steps:
Pause the passive node
using Cluster Admin, stop SQL service
Power down active node server
power down passive node server
after SAN recycle complete
Power up active node server
power up passive node server
restart (resume) passive node
Any insight is greatly appreciated!!
Go ahead and take the entire SQL resource group offline. Then take the
cluster group offline. Down the host nodes, reboot the SAN, then restart
the nodes one at a time.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"RobinMC" <RobinMC@.discussions.microsoft.com> wrote in message
news:78418060-D070-4AEE-BBD7-83D3D827069E@.microsoft.com...
> We are planning a recycle of our SAN to which our active/passive 2-node
> SQL
> cluster is attached. Is there anything special to be aware of?
> We will do the following steps:
> Pause the passive node
> using Cluster Admin, stop SQL service
> Power down active node server
> power down passive node server
> after SAN recycle complete
> Power up active node server
> power up passive node server
> restart (resume) passive node
> Any insight is greatly appreciated!!
|||If you are on a geo cluster (2 disk arrays replicated via a dedicated
technology), first restart the node which was stopped last (for cluster
service).
Guillaume.
==================
"RobinMC" wrote:
> We are planning a recycle of our SAN to which our active/passive 2-node SQL
> cluster is attached. Is there anything special to be aware of?
> We will do the following steps:
> Pause the passive node
> using Cluster Admin, stop SQL service
> Power down active node server
> power down passive node server
> after SAN recycle complete
> Power up active node server
> power up passive node server
> restart (resume) passive node
> Any insight is greatly appreciated!!
cluster is attached. Is there anything special to be aware of?
We will do the following steps:
Pause the passive node
using Cluster Admin, stop SQL service
Power down active node server
power down passive node server
after SAN recycle complete
Power up active node server
power up passive node server
restart (resume) passive node
Any insight is greatly appreciated!!
Go ahead and take the entire SQL resource group offline. Then take the
cluster group offline. Down the host nodes, reboot the SAN, then restart
the nodes one at a time.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"RobinMC" <RobinMC@.discussions.microsoft.com> wrote in message
news:78418060-D070-4AEE-BBD7-83D3D827069E@.microsoft.com...
> We are planning a recycle of our SAN to which our active/passive 2-node
> SQL
> cluster is attached. Is there anything special to be aware of?
> We will do the following steps:
> Pause the passive node
> using Cluster Admin, stop SQL service
> Power down active node server
> power down passive node server
> after SAN recycle complete
> Power up active node server
> power up passive node server
> restart (resume) passive node
> Any insight is greatly appreciated!!
|||If you are on a geo cluster (2 disk arrays replicated via a dedicated
technology), first restart the node which was stopped last (for cluster
service).
Guillaume.
==================
"RobinMC" wrote:
> We are planning a recycle of our SAN to which our active/passive 2-node SQL
> cluster is attached. Is there anything special to be aware of?
> We will do the following steps:
> Pause the passive node
> using Cluster Admin, stop SQL service
> Power down active node server
> power down passive node server
> after SAN recycle complete
> Power up active node server
> power up passive node server
> restart (resume) passive node
> Any insight is greatly appreciated!!
Subscribe to:
Posts (Atom)