Re: Automatic Windows Updates Cause Failover But Resources Don't Start

Tech-Archive recommends: Fix windows errors by optimizing your registry

Windows Updates or not, you likley have issues with your cluster. Verify
that you can successfully fail over resource groups from one node to another
before addressing your WU settings. Many organizations disable Automatic
Updates on their cluster nodes in order to have better control over the
failover process.

Remember that you typically want to schedule these occurrences for preferred
outage windows, as brief as the failovers are...you still want to leverage
some operational procedures and control the service "blips."

--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP


This posting is provided "AS IS" with no warranties, and confers no rights.
"John Toner [MVP]" <jtoner@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OtNYP8aQIHA.3676@xxxxxxxxxxxxxxxxxxxxxxx
Yes, something is causing your cluster resources to fail, trigging
failover.
The specific resource that is failing will be described in the 1069
events.
Can't be more specific without more details.

FYI, you should consider testing updates before rolling them into your
production environment.

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner


"Christopher Beard" <ChristopherBeard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:596C1F60-2258-485D-B0A8-52D02D5CD4A9@xxxxxxxxxxxxxxxx
I have an intermittent problem were one of the nodes in a cluster (SQL or
Exchange) is automatically updated with Windows updates which causes a
failover to the other node when the updated node reboots. That all is
obviously normal, but the second node will take ownership of all the
resources and start a few but not all; especially the Exchange and Sql
services. I am getting errors 1041, 1069, and 1205 from Source: ClusSvc.
Does
anyone know what's happening?
Thanks,
Christopher




.

Relevant Pages

  • Re: Failover Errors
    ... Chuck or anyone, do you now the Microsoft Support number for Clustering? ... Offline and then test a failover. ... it is the cluster log info to see what is happening when the cluster ... Event Category: Network Name Resource ...
    (microsoft.public.windows.server.clustering)
  • Re: 2 node cluster, why failover test fail?
    ... Disconnect the HBA and you'll get a failover. ... there's no point in having just a group with only a disk. ... How can I get resource in "Group 0" failover? ... It seems I can't copy "Cluster ...
    (microsoft.public.windows.server.clustering)
  • Re: Failover Errors
    ... One thing you can do is take the DiskXtender resource in the groupOffline and then test a failover. ... Plus, in this case it is not the system event log info we would need to look at, it is the cluster log info to see what is happening when the cluster tries to take the disk offline in preparation for a failover. ...
    (microsoft.public.windows.server.clustering)
  • Re: ressources unavailables after switch maintenance
    ... service be able to successfully stop Exchange running on the cluster? ... a good connection to both public and heartbeet, the Exchange services just ... Look at the Properties of the resource and check out the ... entire group will failover to another node. ...
    (microsoft.public.windows.server.clustering)
  • Re: Testing Failover
    ... try initate failover more then one time. ... networks you have set the cluster in an arbitration state too. ... group with a new cluster resource, for example a generic program and enter ... when setting the resource to enable you see that the notepad goes up on the ...
    (microsoft.public.windows.server.clustering)