Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Reason for Exchange cluster failover

Posted on 2011-02-22
Medium Priority
Last Modified: 2012-05-11

I'm running Exchange 2007 SP2/Windows 2008 Server in Active-Passive SCC cluster.

Node1: Exchp1.domain.com
Node: Exchp2.domain.com
CMS: ExchCMS.domain.com

Last night, the CMS failed over from P1 to P2 it seems. I notice that because when I connected to ExchCMS this morning, I connected to P2.

I think there were some performance issues on the P1 server, but I'd like to know what actually caused the CMS to fail over? Is there a certain criteria? And what would we look for in the Event Log to show what caused it?
Question by:kam_uk
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
LVL 44

Accepted Solution

Amit earned 2000 total points
ID: 34953912
Check system logs, if you see any errors or warning related to cluster failed. Secondly i would check below

What time did the failover occur?
Has other cluster nodes failover in the past week?
Was there any type of business related operations/maintenance being performed when the failover occurred?
Is there any change control process implemented?
Was there other symptoms before the failover occurred?
Client latency?
Queue buildup?
Unexpected database/transaction log growth?
Network related issues?
Unexpected process terminations?
Performance related (VM Fragmentations, Non-Paged Pool depletions, High RPC, etc…)

Some of the common causes of a cluster failover are:
Server performance
Unexpected process termination
Unresponsive process(es)
Disk subsystem latencies
Anti-Virus configuration
Network changes

Check Cluster.log for more information
LVL 44

Expert Comment

ID: 34953935
Found an article. Please check it. It is related to SCC


Author Comment

ID: 35068131

So we may have had high load on the active node before the failover. In your answer above, you say:

>>>Some of the common causes of a cluster failover are:
Server performance
Unexpected process termination
Unresponsive process(es)
Disk subsystem latencies
Anti-Virus configuration
Network changes

Is there a log or Event ID anywhere that will tell me which one of these caused the CMS to fail over to the passive node?
LVL 44

Expert Comment

ID: 35068744
Check the System Logs. You might see the warning and error messages during that time, when failover was happened.

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question