SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Configuring SQL Server 2005 Failover Settings in Windows Server 2003


Configuring SQL Server 2005 Failover Settings in Windows Server 2003

Author
Message
Richard Lu-422582
Richard Lu-422582
SSC-Enthusiastic
SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)

Group: General Forum Members
Points: 101 Visits: 70
Comments posted to this topic are about the item Configuring SQL Server 2005 Failover Settings in Windows Server 2003
Anipaul
Anipaul
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8765 Visits: 1407
The article can be a base for further research work. Otherwise it is good. Smile



K. Brian Kelley
K. Brian Kelley
Keeper of the Duck
Keeper of the Duck (17K reputation)

Group: Moderators
Points: 17908 Visits: 1917
A follow-on article discussing the networking config (heartbeat, public), would be ideal. Sometimes this configuration can cause a fail-over unexpectedly. I've got that t-shirt.

K. Brian Kelley
@‌kbriankelley
Richard Lu-422582
Richard Lu-422582
SSC-Enthusiastic
SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)

Group: General Forum Members
Points: 101 Visits: 70
I agree follow-on article(s) should be added.

As to the unexpected fail-over, it may indicate that there is a problem/situation in the cluster causing the is-alive check giving false alarm. Usually there could be a problem with the private (team) heart-beat, or the system was in a heavy load, which timed out the is-alive connections during the time span specified. And obviously event logs and the cluster log should be examined for further findings. The automatic failover configuration itself doesn't cause the problem but is a reaction to the is-alive's result. And as a result, the failover was unexpected because of the false alarm. This is a bad example for choosing the automatic failover option. In this case, either resolve the false alarm issue, or disable the automatic fail-over option should be done. This article simply laid out different options and the expecting behaviors along the triggering flow to help people design a proper failover scheme to fit their own needs.
K. Brian Kelley
K. Brian Kelley
Keeper of the Duck
Keeper of the Duck (17K reputation)

Group: Moderators
Points: 17908 Visits: 1917
Richard Lu (3/26/2008)
I agree follow-on article(s) should be added.

As to the unexpected fail-over, it may indicate that there is a problem/situation in the cluster causing the is-alive check giving false alarm. Usually there could be a problem with the private (team) heart-beat, or the system was in a heavy load, which timed out the is-alive connections during the time span specified. And obviously event logs and the cluster log should be examined for further findings. The automatic failover configuration itself doesn't cause the problem but is a reaction to the is-alive's result. And as a result, the failover was unexpected because of the false alarm. This is a bad example for choosing the automatic failover option. In this case, either resolve the false alarm issue, or disable the automatic fail-over option should be done. This article simply laid out different options and the expecting behaviors along the triggering flow to help people design a proper failover scheme to fit their own needs.


Exactly. We're on the same wavelength on this one. Going through these possibilities and explaining what's up and why they trigger the fail-over is something I find myself spending a lot of time discussing with folks I'm bringing up to speed on clustering. Good articles in this area would help a lot. Smile

K. Brian Kelley
@‌kbriankelley
James Cornell-521376
James Cornell-521376
Grasshopper
Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)

Group: General Forum Members
Points: 14 Visits: 273
Good article Richard. Thanks!

James C.

-----
James Cornell
Kainell Database Specialists
http://www.kainell.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search