<div>
I'd add that setting up the Database Availability Group is only about half (or less) of the problem. When your users expect &quot;email to continue to work&quot;, does that mean they're completely unaware that a database failover has occurred? I think you'll find that you need more Exchange servers as well as some router and DNS wizardry to keep your users as happy as possible.
</div>


I'd add that setting up the Database Availability Group is only about half (or less) of the problem. When your users expect "email to continue to work", does that mean they're completely unaware that a database failover has occurred? I think you'll find that you need more Exchange servers as well as some router and DNS wizardry to keep your users as happy as possible.

<div>
<div class="content wysiwyg-content">
I am needing help. I have two offices in different states. I am wanting to build my Exchange environment where there is an Exchange server at each site. If one site goes down I want the other site to take over and have email continue to work. &nbsp;I current have one Exchange 2010 server. How would I do this? Anyone willing to help me get this done? I'n not an Exchange Administrator and have no idea how to get this done.
</div>
</div>


I am needing help. I have two offices in different states. I am wanting to build my Exchange environment where there is an Exchange server at each site. If one site goes down I want the other site to take over and have email continue to work.  I current have one Exchange 2010 server. How would I do this? Anyone willing to help me get this done? I'n not an Exchange Administrator and have no idea how to get this done.

Microsoft Exchange Server

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.