Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 43
  • Last Modified:

Exchange 2013 (On 2008 Server R2) - Cluster issues when quorum lost

9 Exchange 2013 mailbox servers all running on Windows 2008 Server R2. All part of the same DAG (so just one cluster).

Inadvertently, powerer off 5 of these mailbox servers - bad idea. According to my reckoning, due to odd number of members, the quorum should be relying on a majority count of members. Since it no lonfer has a majority then the databases should be dismounted on the remaining servers.

This didn't happen. The exchange databases stayed up - albeit the CAS servers went to 100%.

We then powered back up the 5 servers but the cluster did not recover on its own. On each of the 4 servers that did not power down the cluster status still showed down. A restart of the windows cluster service on each of the 4 servers sorted this out.

Question is :-

1. Any idea why exchange did not dismount DBs when quorum was lost?

2. Why did cluster not recover when the servers were back?
0
paulfoel
Asked:
paulfoel
  • 3
1 Solution
 
Zaheer IqbalTechnical Assurance & ImplementationCommented:
I would say this should be logged with Microsoft.
0
 
paulfoelAuthor Commented:
If my client had a support contract....... :-(
0
 
paulfoelAuthor Commented:
Looks like powerinbg off DAG members is never a good idea.
0
 
paulfoelAuthor Commented:
No other answers provided.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now