DAG Question

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hey guys, I have a quick question.

As I've mentioned before, I am working on an Exchange 2007 -> 2010 migration (CCR->DAG). Brainstorming with the team, we were thinking about deploying Exchange 2010 onto three different sites to make mailboxes available locally on the LAN for the users in each office. From a DR perspective I pretty much got it covered, also other sites must maintain the quorum. We would like for All of this will be done in one domain which spans across these three sites. The WAN is a pretty fast link and works through MPLS.

I should probably deploy multiple DAGs and each DAG will have a witness in its own site so for example DAG1 will have a witness in site 1 and DAG2 will have a witness in site 2, etc

Would this be a good approach in terms of keeping all three DAGs/Quorum operational in other sites in case one site suffers an outage?

The databases will replicate to each site.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Unless I've misunderstood what you're trying to do, it should be possible to use a single DAG. Assuming you have two DBs one server per site:

Site1MBXSrv

Site1DB1 - Active
Site1DB2 - Active

Site2DB1 - Witness
Site3DB2 - Witness

Site2MBXSrv

Site2DB1 - Active
Site2DB2 - Active

Site1DB2 - Witness
Site3DB1- Witness

Site3MBXSrv

Site3DB1 - Active
Site3DB2 - Active

Site1DB1 - Witness
Site2DB2 - Witness

In that example, if you lost Site3, the Site3DBs would become active on Site1 and Site2. You could have multiple servers per site in the above example, you'd just have to distribute the databases accordingly. Unless you have more than sixteen servers/sixteen databases, it should be pretty straightforward with a single DAG

 

Gotcha, thanks for the reply, I actually want to have 2 MBX servers in each site but that would created quite a few DB's..