DAG Failover

I have a 3 member dag all part of the same site, same network running on VM

ExchDAG01 with members
MBX01
MBX02
MBX02

I have setup 2 nics, disabled the recommended features on the cluster NIC.
User run Exchange online, so not in cache mode



When i fail over a database from one active DAG member to the other, users get disconnected for 5-10 seconds. I can figure out why this happens.  With Exchange 2010 it was seamless

Any suggestions would be great.  Thanks
Mike khodabakhshiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mike khodabakhshiAuthor Commented:
I have also tried pointing my computer directly to one of the CAS servers via host file to see if it has anything to do with NLB
Same results
0
Mike khodabakhshiAuthor Commented:
Just more information on this, even when I reboot the secondary node (passive) I still see outlook disconnect and reconnect??Which is very odd
0
Mike khodabakhshiAuthor Commented:
Thanks for anyone to add something to this please??  I cant find a simple article that says DAG failover  2013 should be seamless to users.
0
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.

MAS (MVE)EE Solution GuideCommented:
Here is a similar thread regarding the delay for outlook to reconnect when a database switch over to another server. Please read this completelyhttps://social.technet.microsoft.com/Forums/exchange/en-US/85a04340-07bf-4466-b192-dfee4e719d10/exchange-dag-failover-slow-outlook-reconnect?forum=exchangesvravailabilityandisasterrecovery
0
AmitIT ArchitectCommented:
Purchase and use Layer 7 load balancer. NLB is no more recommended with Exchange. Also this time taken to switch over could be product bug, as now with 2013 they merged almost everything into mbx role and CAS plays a stateless role. like a proxy server, in 2010 CAS use to do lot of  things. I don't have 2013 to test, I suggest you to open MS case and ask for the solution.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Gareth GudgerCommented:
Also, they mentioned at MEC 2014 that the recovery time was greatly reduced if you switched to MAPI over HTTP versus the traditional RPC over HTTP.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.