SQL Server Performance

Cluster Failback not working

Discussion in 'SQL Server 2005 Clustering' started by Rick H., Jun 23, 2010.

  1. Rick H. New Member

    Once a month Micrsoft Security updates are installed. The primary node receives the updates first, reboots and completes the Failover to the passive node. The failback settings in the Cluster Administrator are set to:
    Allow failback
    Failback between 2 and 8 hours
    Failback never occurs
    Plus, the Passive Node receives it updates the followng day, reboots and STILL retains the SQL Cluster Group even though it rebooted.
    Any ideas???
    Rick H.
  2. melvinlusk Member

    What are the settings for failover?
    I find failback to be extemely dangerous. If there is a problem with node 1, and you fail things over, it could potentially try to fail back to node 1. Your mileage may vary.
  3. satya Moderator

    The best point of investigation is to check thru CLUSTER.LOG in order to see if there are any compending issues for failback.
    what happens if you manually failback to previous node?

Share This Page