Re: Cluster does not restart SQL group after network failure

From: Geoff N. Hiten (SRDBA_at_Careerbuilder.com)
Date: 11/23/04

  • Next message: R P: "Re: Win2003 and MSDTC" 
    Date: Mon, 22 Nov 2004 21:40:13 -0500

    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
  • Next message: R P: "Re: Win2003 and MSDTC"

    Relevant Pages

    • Re: SQL Server Cluster
      ... > activity times to shift cluster resources. ... > host nodes with different elevels of critical updates if you can't move ... > I support the Professional Association for SQL Server ...
      (microsoft.public.sqlserver.clustering)
    • Re: Network cluster problems
      ... >connection, ... W2K will no long failover if you lose network ... the IP resources ... >in the cluster will fail taking down any network names ...
      (microsoft.public.windows.server.clustering)
    • Re: Network cluster problems
      ... it is recommended to disable media sense on the "heartbeat" network ... connection, ... when you lose network connectivity the IP resources ... You're trying to connect to the cluster ...
      (microsoft.public.windows.server.clustering)
    • Re: How to configure cluster if I am going to setup SQL 2005 for Failo
      ... Cluster nodes can not be on different physical networks - period. ... while the rest of the nodes run a single instance of SQL Server. ... This includes network cards, drives, etc. ... To keep the Private network as fault tolerant as possible, ...
      (microsoft.public.windows.server.clustering)
    • Re: msdtc is causing my cluster to be unavailiable via its virtua
      ... private network interfaces? ... I see that the IP in the SQL Server cluster resource group is named SQL IP ... > MSDTC Group has the MSDTC Network name, MSDTC IP Address=10.0.0.60, ...
      (microsoft.public.sqlserver.clustering)
    • Quantcast