Hi all,
I've build two Exchange 2013 server environment CAS and Mbx -roles with both server. Building DAG went Ok and it looks like cluster is working underneeth. But, doing failover by Activating another copy of database, the first one goes Failed-mode. Manual suspend and seeding will have to be done to get it to healthy state again. I have tested a few powershell commands and checked network configurations, they seem to be correct as well. To clarify scenario, the activated one will start working fine after failover, so to be passive one failes.
Interesting is that when creating new database, it failsover fine one or two times without problems, but after some time that one too starts the same behavior described earlier. Event Ids don't tell much, something about replication, that has not lead anywhere so far (I can post the event id later).
Any ideas?
Servers are build on Vmware. Replication network is build with IPs on same subnet, and there is a separated from Mapi network (which work fine for clients).
Regards,
RJ