Re: Cluster does not restart SQL group after network failure

From: Dan (Dan_at_discussions.microsoft.com)
Date: 11/23/04 

Date: Tue, 23 Nov 2004 07:41:14 -0800

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
>
>
>

Relevant Pages

  • Re: Cluster does not restart SQL group after network failure
    ... Unfortunately, until the network resource is restored, no node ... including the Network Name and the SQL Server. ... cluster will bring the system online. ... > virtual SQL and Windows IP address resources went down and did not come up ...
    (microsoft.public.sqlserver.clustering)
  • Re: about MSSQLSERVER run as LocalSystem
    ... If you need a SQL Server to be able to access other network ... running under a domain account. ... access to network resources. ...
    (microsoft.public.sqlserver.security)
  • Re: proper naming of a domain
    ... The primary reason for not being able to see resources/browse etc during a VPN is that the IPschema of remote network is the same as the LAN that you are connecting to. ... from home I can Connect to the server and it tells me that I am connect to ... resources it tells me that the path cannot be found. ...
    (microsoft.public.windows.server.sbs)
  • Re: Detect open windows shares?
    ... to know their names is to browse the network neighborhood. ... The WNetOpenEnum function starts an enumeration of network resources or existing connections. ... RESOURCE_CONTEXT Enumerate only resources in the network context of the caller. ... To obtain a description of the error, call the WNetGetLastError function. ...
    (comp.lang.perl.misc)
  • ODBC Connection with SQL Managed Provider
    ... on a "network drive". ... database using the Microsoft .NET Framework 1.1 Data Provider for SQL ... authorizing the user against a table in the SQL server database. ... for the app to display the "splash" screen (which is the first thing it does ...
    (microsoft.public.dotnet.framework.adonet)
Quantcast