|
|
You're in the
sql server clustering
group:Cluster does not restart SQL group after network failure
sql server clustering:
We have just rebuilt a SQL 7.0/NT cluster with Windows 2003/SQL2000 in an active/passive configuration using 2 nodes. During the course of testing it we had a general network failure in which the network was unavailable. The virtual SQL and Windows IP address resources went down and did not come up automatically once the network was available again. The nodes are configured for automatic failback. I can't imagine that in the 2 1/2 years the original cluster was running that we never once had the network go down, but I do know that during that time I never had a outage where I had to manually move the cluster group (which causes the cluster to re-initialize both resources and brings everything back to normal). I'm thinking that maybe I'm missing a dependency somewhere or something's changed between NT and 2003 that I'm not accounting for. Anyone seen this or have any tips? Thanks in advance!
Nope, that is pretty much expected behavior. The cluster manager will try
and restart the resources on each possible node until the retry count is exhausted. Unfortunately, until the network resource is restored, no node has the ability to run the SQL group. With the physical network port offline, the IP address(es) will not come online. Nothing dependant on them will come online, including the Network Name and the SQL Server. If the network comes back before the retry timeout and count is exhausted, the cluster will bring the system online. Otherwise it stays down. -- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org [quoted text, click to view] "Dan" <Dan@discussions.microsoft.com> wrote in message news:74592016-0B61-4834-8C28-1AD1B864B688@microsoft.com... > All, > > We have just rebuilt a SQL 7.0/NT cluster with Windows 2003/SQL2000 in an > active/passive configuration using 2 nodes. During the course of testing it > we had a general network failure in which the network was unavailable. The > virtual SQL and Windows IP address resources went down and did not come up > automatically once the network was available again. The nodes are configured > for automatic failback. > I can't imagine that in the 2 1/2 years the original cluster was running > that we never once had the network go down, but I do know that during that > time I never had a outage where I had to manually move the cluster group > (which causes the cluster to re-initialize both resources and brings > everything back to normal). > > I'm thinking that maybe I'm missing a dependency somewhere or something's > changed between NT and 2003 that I'm not accounting for. Anyone seen this or > have any tips? Thanks in advance! > > -Dan
Geoff,
Thanks for the post! I guess I'll just have to make sure the retry & timeout are set high. [quoted text, click to view] "Geoff N. Hiten" wrote:
> Nope, that is pretty much expected behavior. The cluster manager will try > and restart the resources on each possible node until the retry count is > exhausted. Unfortunately, until the network resource is restored, no node > has the ability to run the SQL group. With the physical network port > offline, the IP address(es) will not come online. Nothing dependant on them > will come online, including the Network Name and the SQL Server. If the > network comes back before the retry timeout and count is exhausted, the > cluster will bring the system online. Otherwise it stays down. > > -- > Geoff N. Hiten > Microsoft SQL Server MVP > Senior Database Administrator > Careerbuilder.com > > I support the Professional Association for SQL Server > www.sqlpass.org > > "Dan" <Dan@discussions.microsoft.com> wrote in message > news:74592016-0B61-4834-8C28-1AD1B864B688@microsoft.com... > > All, > > > > We have just rebuilt a SQL 7.0/NT cluster with Windows 2003/SQL2000 in > an > > active/passive configuration using 2 nodes. During the course of testing > it > > we had a general network failure in which the network was unavailable. > The > > virtual SQL and Windows IP address resources went down and did not come up > > automatically once the network was available again. The nodes are > configured > > for automatic failback. > > I can't imagine that in the 2 1/2 years the original cluster was running > > that we never once had the network go down, but I do know that during that > > time I never had a outage where I had to manually move the cluster group > > (which causes the cluster to re-initialize both resources and brings > > everything back to normal). > > > > I'm thinking that maybe I'm missing a dependency somewhere or something's > > changed between NT and 2003 that I'm not accounting for. Anyone seen this > or > > have any tips? Thanks in advance! > > > > -Dan > >
Be careful adjusting those numbers. TOo high can cause just as many
problems as too low. Given the frequency of the network outage and the fact that something like that will NEVER go unnoticed, I would not change anything. The cluster failover is designed to reduce the typical 30-45 minute human reponse time for a down server. You shouldn't expect the clustering software do deal with anything beyond that scope. Adjusting the parameters to try and expand that coverage will only expose a gap somewhere else. Just document a cluster check as part of your network failure recovery procedure and you will be fine. -- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org [quoted text, click to view] "Dan" <Dan@discussions.microsoft.com> wrote in message news:34AB2749-41BF-4A68-8E55-04AEAAE75C38@microsoft.com... > Geoff, > > Thanks for the post! I guess I'll just have to make sure the retry & > timeout are set high. > > "Geoff N. Hiten" wrote: > > > Nope, that is pretty much expected behavior. The cluster manager will try > > and restart the resources on each possible node until the retry count is > > exhausted. Unfortunately, until the network resource is restored, no node > > has the ability to run the SQL group. With the physical network port > > offline, the IP address(es) will not come online. Nothing dependant on them > > will come online, including the Network Name and the SQL Server. If the > > network comes back before the retry timeout and count is exhausted, the > > cluster will bring the system online. Otherwise it stays down. > > > > -- > > Geoff N. Hiten > > Microsoft SQL Server MVP > > Senior Database Administrator > > Careerbuilder.com > > > > I support the Professional Association for SQL Server > > www.sqlpass.org > > > > "Dan" <Dan@discussions.microsoft.com> wrote in message > > news:74592016-0B61-4834-8C28-1AD1B864B688@microsoft.com... > > > All, > > > > > > We have just rebuilt a SQL 7.0/NT cluster with Windows 2003/SQL2000 in > > an > > > active/passive configuration using 2 nodes. During the course of testing > > it > > > we had a general network failure in which the network was unavailable. > > The > > > virtual SQL and Windows IP address resources went down and did not come up > > > automatically once the network was available again. The nodes are > > configured > > > for automatic failback. > > > I can't imagine that in the 2 1/2 years the original cluster was running > > > that we never once had the network go down, but I do know that during that > > > time I never had a outage where I had to manually move the cluster group > > > (which causes the cluster to re-initialize both resources and brings > > > everything back to normal). > > > > > > I'm thinking that maybe I'm missing a dependency somewhere or something's > > > changed between NT and 2003 that I'm not accounting for. Anyone seen this > > or > > > have any tips? Thanks in advance! > > > > > > -Dan > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |