Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Win2012r2 failover cluster manger not matching Exch2013cu21 EAC's DAG settings

$
0
0

Hi there,

I have two exch2013cu21 std servers (Server A & B) in two differnet locations with DAG. 
Recently found that server B with eventid 7031 shown cluster service has issue.
I cannot start the service manually. It shown “service-specific error code 2”.

Stupid enough, somehow I run “cluster node /force” into Server A wrongly. Then email service stopped.
Server A cluster service same as Server B, stopped and unable to start manually.

Eventually I have to create new cluster in Failover Cluster Manager (old name: DAG1; new name with new IP: DAG3) then the cluster service started. I can mount the database in EAC manually. The email services back to normal.

However there's still some abnormaly. Server A & B cannot connect back DAG1 in Failover Cluster Manager (nothing shown after click “connect to cluster”), but EAC shown DAG1 normal.

How can I connect DAG1 back to Failover Cluster Manager and remove DAG3 in Failover Cluster Manager?

Now what's the most appropriate method to fix?  

Connect DAG1 back to Failover Cluster Manager & remove DAG3 in Failover Cluster Manger?

Create new DAG3 in EAC & remove DAG1 in EAC?

Many thx!




Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>