<div>
you will need an extra server in the main site to act as a share witness (no need for it to be an exchange server) to implement your DAG that's it<br />
<br />

</div>


<div>
I understand that but its the internet line going down which I feel is the issue as where should the witness server be as both servers need to see it to bring the DB online?
</div>


<div>
if the internet goes down the server not being able to see the sharewitness will go down...<br />
<br />
so maybe i miss understood your question
</div>


<div>
yes so i need to make sure they can both see the witness server at all times is a third site the answer?
</div>


<div>
both being able to see the witness at all times will drag you into a split brain scenario<br />
<br />
suppose <br />

<div class="bullet">
server 1 sees the witness so it thinks server 2 is down and keep the db up
</div>
<div class="bullet">
server 2 sees the witness so it thinks server 1 is down and brings the db up 
</div>
<br />

</div>


<div>
where should the witness server be? main site or site 2?
</div>


<div>
in the site you want to go down if the connection between the 2 is down
</div>


<div>
but what if the 2nd site internet connection goes down does this mean that site1 DB will fail?
</div>


<div>
first let me fix a typo i did in my previous post the share witness should be in the site you DON'T want to go down if the wan link between both goes down.<br />
<br />
the idea is that you have 3 voters node1 node2 and the SW. at anytime any node should be able to see 2 out of 3 to decide he is not down but the other node. <br />
<br />
going back to your original idea of a 3rd site it would be possible assuming that node1 and node2 can communicate together thru this 3rd site also
</div>


<div>
i understand but both of the servers are in different locations, which means if the internet goes down at the site with 1 exchange and witness server surly this means the DB wont mount?
</div>


<div>
If internet goes down at the site with file share witness the db in the other site will not mount.<br />
<br />
Nothing we can do about it this is by design
</div>


<div>
so my idea of the third site is a good idea or not?
</div>


<div>
again the problem with the 3rd site is that you might end up with a split brain as we discussed before
</div>


<div>
ok, I assume you understand my problem here I need the email system to be up all the time and if any site goes down they can point to the other and continue working.<br />
is this not the norm? is there not a better solution? my client wants the exchange system to be virtually bomb proof as he is always travelling and sometimes there is no one in the office for weeks.<br />

</div>


<div>
&gt; is this not the norm<br />
no it is not, the problem is DAG across sites was designed to be Active / Passive and not Active/Active so you cannot have live databases at the same time in 2 different sites and be able to accommodate link failures. I know it is kind of hard to believe but this is the way it is. sorry<br />
<br />
&gt;&nbsp; there not a better solution?<br />
The solution is to have 4 exchange servers (2 in each sites) configured in 2 DAGs each one acting as active / passive<br />
<br />
<br />
from a technical perspective you can hack the system by putting your share witness in a 3rd site as you previously said and blocking the databases to auto-mount each in a different site.<br />
<br />
In that case we are taking manually care of the split brain syndrome but I can't say it is a fool proof solution since the slightest error would lead to split brain and huge problems and that is why i never mentioned the &quot;solution&quot; till now
</div>


<div>
I have been doing some more research would the SP1 update with DAC not help?
</div>


<div>
No, again DAC, has nothing to do with this, it is to avoid split brain if the main site is back online before the network .
</div>


<div>
This is what we have read:-<br />
<br />
DAC mode is configured to avoid a “split brain syndrome”. I will explain with an example. Let’s say we have a four member DAG, with two servers in each datacenter. The primary datacenter hosts the witness server and hence will always be in quorum. Now, let’s say that a power outage occurs in the primary datacenter and the exchange admin activates the secondary datacenter with an alternate file share witness. <br />
<br />
When the power is restored in the primary site, servers come online quicker than the WAN links. Hence, when the two DAG members and witness server comes online, it has a quorum (majority) and will try to activate the databases. This will cause a “split brain syndrome” where both datacenters think that they are hosting the active databases.<br />
<br />
DAC mode was introduced to avoid this situation. When DAC mode is enabled and the DAG members come back online, they will leverage a protocol called Datacenter Activation Coordination Protocol (DACP) before trying to mount the databases. &nbsp;The DACP is used to determine the current state of the DAG and whether Active Manager should try to mount the databases or not.<br />
<br />
Now for the technical bit as to how DAC works! <br />
<br />
Active Manager stores a bit in memory (either a 0 or &nbsp;1) that tells the DAG whether it's allowed to mount local databases that are assigned as active on the server. When a DAG is running in DAC mode, each time Active Manager starts up, the bit is set to 0, which means that it isn't allowed to mount databases. When in DAC mode, the server must try to communicate with all other members of the DAG that it knows to get another DAG member to give it an answer as to whether it can mount local databases that are assigned as active to it. The answer comes in the form of the bit setting for other Active Managers in the DAG. If another server responds that it’s bit is set to 1, it means that servers are allowed to mount databases. Hence, the server starting up sets its bit to 1 and mounts its databases. <br />
<br />

</div>


<div>
this is exactly what I said in my previous answer... please explain what are you trying to say 
</div>


<div>
well it seems you might be lucky Shudown says it will work on 1 ip<br />
<br />
<a href="http://www.shudnow.net/2008/08/21/how-anonymous-relay-works-in-exchange-2007/" rel="ugc">http://www.shudnow.net/2008/08/21/how-anonymous-relay-works-in-exchange-2007/</a><br />
<br />

</div>


<div>
kindly ignore my last post I was trying to answer another thread...<br />
<br />
this is exactly what I told you about DAC what is your question ?
</div>


<div>
Hi Akhater<br />
<br />
2 sites over WAN VPN link both on server 2008 Ent with Exchange 2010. We want to failover to the second exchange if the main site goes down or internet goes offline.<br />
<br />
Were getting so confused and can't believe this is not an option or easy to do.<br />
<br />
Is this an option with 4 exchange servers 2 at each site?<br />
<br />
Regards<br />
<br />
MFG
</div>


<div>
the only way to accommodate for link failures (i.e. internet going down) is having 2 DAGs <br />
<br />
so 4 servers would surely work Server1 active site1 passive site1 and Server2 active stie2 and passive site1
</div>


<div>
Thanks, is there anything else we should think about.
</div>


<div>
yes use exchange 2010 sp1 and put both dags in DAC mode
</div>


<div>
I presume this is what data centres have to do?
</div>


<div>
<div class="content wysiwyg-content">
Hi I have a client who currently has 2 Windows Server 2008 Ent machines and we have setup a site to site VPN connection which works perfect, however they are currently only running exchange 2010 Std on the server in there main office the other server is just currently being used for DFS-R.<br />
Basically what they want is a failover site as they are out on the road a lot so incase of the internet going down at the main site the passive copy would come online at the second site.<br />
<br />
Now from what what I understand I would need either a witness server or another hub transport server in place so each server know whats going on?<br />
<br />
Basically I need to know do I need the witness server at a 3rd site or is there a better way of doing this maybe not even using DAG's?<br />
<br />
I look forward to your comments, thank you.
</div>
</div>


Hi I have a client who currently has 2 Windows Server 2008 Ent machines and we have setup a site to site VPN connection which works perfect, however they are currently only running exchange 2010 Std on the server in there main office the other server is just currently being used for DFS-R.
Basically what they want is a failover site as they are out on the road a lot so incase of the internet going down at the main site the passive copy would come online at the second site.

Now from what what I understand I would need either a witness server or another hub transport server in place so each server know whats going on?

Basically I need to know do I need the witness server at a 3rd site or is there a better way of doing this maybe not even using DAG's?

I look forward to your comments, thank you.

Exchange 2010 DAG Site to Site Configuration

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.