Windows 2012 Cluster with Exchange 2013 DAG
hi,
i have question regarding windows 2012 failover clustering.
we have windows 2012 running exchange 2013 dag. 8 nodes 1 witness server
there few instances 1 of nodes lost quorum due network issues. when ever happens cluster service goes in restarting (crashing). i tried change cluster service manual , start but, keep crashing until restart server after works fine node once again gets added quorum without issues.
my question - normal behavior if node lose quorum cluster service keep restarting until restart server? or there way bring server in quorum without restart of server.
clussvc.exe version 6.2.9200.21268
error
the cluster service service terminated unexpectedly. it has done 15 time(s). the following corrective action taken in 60000 milliseconds: restart service.
thanks,
raman
hi raman03,
it seems known issue, please first install following hotfix,
deadlock makes server farm sites unavailable when backup job fails
http://support.microsoft.com/kb/2964441/en-us
intermittent i/o stalls on thinly provisioned volumes when file-delete notifications enabled
https://support.microsoft.com/en-us/kb/2996802
if above hotfix not work please install following recommended hotfix , updates, if have backup soft cluster backup please not backup cluster witness, monitor issue again.
recommended hotfixes , updates windows server 2012-based failover clusters
https://support.microsoft.com/en-us/kb/2784261
more information:
windows 2012 cluster issue, exchange 2013cu2 mailbox both vms unexpectedly restarting
i’m glad of you!
please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com
Windows Server > High Availability (Clustering)
Comments
Post a Comment