Exchange 2010 DAG Automatic Failover Testing/Issue. Not always automatically failing over to health

Posted by Richard on Server Fault See other posts from Server Fault or by Richard
Published on 2010-03-10T21:12:19Z Indexed on 2010/03/27 0:13 UTC
Read the original article Hit count: 1354

Ok I've got 2 exchange 2010 servers that run client access/hub transport/mailbox roles and one exchange 2010 server running just client access/hub transport roles and acts as my bridgehead. The two mailbox servers are running one database setup in a DAG. Server A shows the DB Mounted and Server B shows Healthy. If I reboot Server A via windows GUI Server B switches from healthy to mounted and I see hardly any interruption in service using Outlook 2007. Server A shows "Service down", then "Failed" then "Healthy" and leaves the DB mounted on Server B. This is how it should work, so far so good.

Now if I test Server A being shut down cold, or unplugging both nics from network to simulate failure, Server B switches from Healthy to Mounted and server A switches to "Service Down" but my outlook client never connects to the DB mounted on server B! I can connect to server C (client access/hub transport) and get to my email and even send new email out, but incoming email doesn't deliver until Server A is brought back online and it's DB goes back to Healthy status.

So I don't understand why it auto fail-overs when I reboot the server with the mounted DB copy, causing very little outlook 2007 hiccup if any. But when I shutdown or DC the mounted DB server it DOES mount the healthy copy but outlook 2007 clients can't connect..

I hope the picture I'm trying to paint makes some sense, it's driving me a little batty. Any help would be appreciated!

© Server Fault or respective owner

Related posts about failover

Related posts about high-availability