Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Configuring SQL Server 2005 Failover Settings in Windows Server 2003 Expand / Collapse
Author
Message
Posted Tuesday, March 25, 2008 12:23 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, June 10, 2011 2:04 PM
Points: 65, Visits: 67
Comments posted to this topic are about the item Configuring SQL Server 2005 Failover Settings in Windows Server 2003
Post #473881
Posted Tuesday, March 25, 2008 5:32 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, July 17, 2014 10:36 PM
Points: 5,297, Visits: 1,378
The article can be a base for further research work. Otherwise it is good. :)


Post #473946
Posted Tuesday, March 25, 2008 11:40 AM


Keeper of the Duck

Keeper of the Duck

Group: Moderators
Last Login: Thursday, July 10, 2014 1:34 PM
Points: 6,623, Visits: 1,855
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, CISA, MCSE, Security+, MVP - SQL Server
Regular Columnist (Security), SQLServerCentral.com
Author of Introduction to SQL Server: Basic Skills for Any SQL Server User
| Professional Development blog | Technical Blog | LinkedIn | Twitter
Post #474273
Posted Wednesday, March 26, 2008 9:37 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, June 10, 2011 2:04 PM
Points: 65, Visits: 67
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.
Post #474855
Posted Thursday, March 27, 2008 3:31 PM


Keeper of the Duck

Keeper of the Duck

Group: Moderators
Last Login: Thursday, July 10, 2014 1:34 PM
Points: 6,623, Visits: 1,855
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. :)


K. Brian Kelley, CISA, MCSE, Security+, MVP - SQL Server
Regular Columnist (Security), SQLServerCentral.com
Author of Introduction to SQL Server: Basic Skills for Any SQL Server User
| Professional Development blog | Technical Blog | LinkedIn | Twitter
Post #475780
Posted Tuesday, April 29, 2008 10:34 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, April 22, 2013 11:35 AM
Points: 10, Visits: 273
Good article Richard. Thanks!

James C.


-----
James Cornell
Kainell Database Specialists
http://www.kainell.com
Post #492329
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse