For Exchange Server 2016 the high availability building block is the database availability group (DAG). Exchange 2016 DAGs are very similar to Exchange 2013 DAGs however there are some new features and behaviours to be aware of, which I’ll demonstrate in this article series. I’ll also cover:
- Installing a new Exchange Server 2016 database availability group
- Managing database copies for Exchange Server 2016 database availability groups
- Database switchovers and failovers for Exchange Server 2016 database availability groups
- Reseeding a failed database copy in an Exchange Server 2016 DAG
- Recovering a failed Exchange Server 2016 DAG member
Let’s begin with an overview of database availability group concepts.
Exchange Server 2016 DAG Concepts
Database availability groups can contain up to 16 Exchange 2016 mailbox servers, each of which hosts copies of one or more databases that are replicated with database copies on other members of the same DAG.
When a DAG is first created it has zero members. A minimum of two members is required for the DAG to provide high availability. Two-member DAGs are reasonably common as a simple HA deployment of Exchange, for example in the diagram below two Exchange 2016 servers and a file share witness make up a database availability group.
Database Availability Groups and Quorum
Exchange Server DAGs make use of an underlying Windows Failover Cluster. You don’t need to create, configure, or even touch the Windows Failover Cluster using cluster management tools, except in specific maintenance scenarios that are clearly documented. When you add members to a DAG the failover clustering components are automatically installed and configured for you.
Quorum is the voting process that the cluster uses to determine whether the DAG should remain online or go offline. If the DAG goes offline all of the databases in the DAG are dismounted and inaccessible to end users, causing an outage.
There are two quorum models:
- Node Majority – when the DAG has an odd number of members the file share witness is not required for the quorum voting process, because the DAG members can determine a “majority” themselves. For example, if one DAG member fails, 2/3 DAG members are still online (a majority) and the DAG can remain online. If two DAG members fail, 1/3 DAG members are still online, which may result in quorum being lost and the DAG going offline.
- Node and File Share Majority – when the DAG has an even number of members the file share witness is included in the quorum voting process to ensure that a “majority” can be determined. For example, in a two-member DAG if one member fails, 1/2 members are still online (not a majority), but you would expect the DAG to be able to withstand a single node failure. The file share witness is used as the tie-breaker, meaning 2/3 “votes” are still available, and the DAG can stay online. Similarly with a four-member DAG, if two members failed, with the file share witness there are still 3/5 “votes” online, so the DAG can stay online.
I wrote above that in some failure scenarios the DAG may lose quorum and go offline. In some circumstances the DAG can sustain a majority of nodes being offline if there has been sequential failures. This is thanks to a feature of Windows Server 2012 clusters called Dynamic Quorum.
Database Copies and Continuous Replication
Each member of the Exchange 2016 DAG hosts one or more database copies, and participates in the process of continuous replication to keep those database copies updated with changes. The Exchange 2016 server edition determines how many database copies a DAG member can host. A Standard edition server can host up to 5 database copies, and an Enterprise edition server can host up to 100 database copies.
Exchange 2016 DAG members can host a mix of active and passive database copies, because the switchover/failover occurs at the database level, not the server level. So there is no concept of an “active server” or a “passive server”.
During continuous replication the transaction log data that is generated on the active database copy is shipped across the network to the DAG members hosting passive database copies. Those DAG members then replay the transaction log data to update their passive database copy. Replay can occur immediately, or it can be configured to be a lagged database copy.
There is not a special installation of Exchange Server 2016 for DAG members. An Exchange 2016 mailbox server can be added to a DAG, or removed from a DAG, at any time without impacting the databases and other services hosted on that server. Incremental deployment makes it possible for organizations to deploy a single server today, and then scale out to a DAG at a later time if necessary, without any impact to production services.
Database Availability Group Networks
A DAG network is one or more IP subnets that the DAG members are directly connected to. Every Exchange 2016 database availability group has at least one DAG network that is used for client traffic. A DAG can also have one or more separate, dedicated networks for database replication traffic.
With the speed of modern networks it is generally recommended to use only one DAG network, which is simpler to manage and creates a more predictable failure scenario.
An Exchange 2016 database availability group provides high availability for Exchange within a single datacenter or Active Directory site. Exchange 2016 DAGs can also be deployed across multiple datacenters to provide site resilience as well, allowing the Exchange services to remain online in the event of a complete datacenter outage.
In this article I’ve covered an introduction to Exchange Server 2016 database availability groups by explaining some of the fundamental concepts of DAGs. In the next part of this article series I’ll walk through the step by step process of creating an Exchange 2016 database availability group.
Hello Paul, I am not sure if this exact question has been answered before. I have a an existing 2010 DAG with 2 members and I am looking to create a new DAG using 2 Exchange 2016 servers. We are in an Exchange Hybrid setup and most mailboxes have been already migrated already to Exchange Online.
I would like to create a new DAG and a mailbox database on the 2016 servers and then move any mailboxes that must remain on prem to the new DAG. I would then decommission the 2010 Exchange servers as they are approaching end of life.
I would like to setup a the new 2016 DAG without and administration point. The 2016 servers have been created with 2 nics each and with the correct settings for the replication NIC.
The replication subnet on all 4 servers is the same, example 192.168.1.0/24.
Question 1 – If i create the 2016 DAG using the same replication subnet, is that going to mess up the existing 2010 DAG?
Question 2 – Do you recommend setting up the DAG manually or letting Exchange auto configure.
Thanks in advance for your feedback.
I have the same question. Have two Exchange 2016 servers in a DAG both running on Windows Server 2012R2. Need to get the Exchange databases on servers running Windows Server 2016. Can’t add new Exchange server to DAG if different OS. Can I create new DAG, add new Exchange servers and migrate databases? If so, how to configure subnets?
Iknow this is an old article but I hope you can still help. We have one DAG on 2 – 2016 servers with one witness server on the DNS server. When one exchange server goes down, most internal clients cannot connect from outlook for their mail. Others do not. I think everyone has their outlook clients pointed to a particular server (i.e. some go to mail1 and others point to mail2). How do I get all clients to work after one of servers go down? We don’t have a load balancer. I saw info about creating a round robin DNS with a generic FQDN like “mail” and put in the IPs of both servers for “mail” then point the clients to that. Is that the way to go or is AutoDiscover supposed to take care of it?? Will that cause issues in the long run? How long does it take for a client to grab the IP of the other server? Is it based on my refresh time in DNS or Expire Time?
I have an existing 2 node DAG (1 on-prem and 1 on DR site). How can I accomplish adding a 3rd node to the existing DAG? How do I properly setup the new Exchange server 2016 as a member of the existing DAG?
I am looking for a clear definitive answer on this one. I have a 2 node DAG and a FSW. Node A and FSW are in primary datacenter, Node B is in secondary datacenter. We recently moved all of our DBs active copies to the secondary datacenter on Node B.
We then lost our primary datacenter, so Node A and FSW went completely dark. What would the expected behaviour be here for the mounted DBs in secondary datacenter? As one DAG member was offline along with FSW, shouldn’t these active DBs have dismounted automatically?
I am told they remained mounted from the console/GUI perspective but we had user complaints they couldn’t access email. I am seeing contradicting information on what will happen if you lost the link between your 2 DCs and your active DBs are on a different site to the FSW?
You need to enable DataCenterActivation mode for this to work correctly. But this will require a (small) manual task to enable smooth/correct failover.
E.g. if (AD)site A goes down, your mailboxes will be mounted on your passive Exchange servers, but exchange will not mark the servers in Site A as down. You should then run ‘stop-databaseavailabilitygroup -identity -ActiveDirectorySite ‘Site A’
this will enable full functionality of Site B even without access to the FSW and no hiccups when Site A comes back online. after Site A is deemed fully only again, you can run ‘restore-databaseavailabilitygroup -ActiveDirectorySite ‘Site A’
Good evening Paul
I’m reading your post(s) about DAG, I read also on other sites (your posts are always clear and well explained).
A DAG seems to be useful if we want to provide high availability for users, on the primary office site, using a quorum witness.
In case I have only one exchange server on the primary Office site, and would like a second Exchange server in a DR site (no users on that site), is it possible to have a DAG that will have both servers (ExchangeOffice and ExchangedDR) as members ? Sites have different IP range, Sites have their own domain controler named DC.domain.local and DR.domain.local.
Will this configuration assure me that users will have access to their emails in case the ExchangeOffice server goes down (slower acces because of the inter-site link) ?
In case the Office site goes down, with no more quorum (located at the office that is no longer working) will the ExchangeDR database start with an unreachable quorum ? Is the solution (I think you mentioned it) of having a Quorum on a shared folder on azure the solution so quorum will always be reachable ?
I think this is what you mentioned as “site resilience”, so I basically supposed there is one DAG with members on two different sites but I doubt it is as easy as that.
thank you if you can just clarify this point so I will stop beeing stuck for nothing.
Customer have a Primary Exchange, and would like to have another in DR site, the intranet bandwidth is about 30mbps. ( wireless connection between 2 sites )
possible to run it ?
Very useful article as ever. I can’t decide between 2 or 3 members on my DAG. I run a single site Exchange 2016 installation with about 50 mailboxes. All hosted in house across a couple of VM hosts running Server 2016 on ESXi. The 2 current members aren’t on the same VM.
Is it worth sticking a new server on there or just pointless replication?
I am rebuilding a DAG server. I want to remove then create the DAG with same configuration.
Are there any implications that can happen when I remove the DAG? Can I use the same configuration? Thanks! 🙂
I have two data centers at locations with active user population. I want each location users to connect to their respective Data Center mailbox servers. Like previous exchange versions, Exchange 2016 also allow create separate DAG for separate location with active user population?
Please shed some light on it.
Yes. If that is your requirement you can do separate DAGs and use the “bound namespace” model. Microsoft has good documentation on this approach, though it is not the preferred approach.
Hope you are ok and well. Thank you for all your articles on line. Very clear and intuitive.
I have a quick question regarding the “Exchange Server Role Requirements Calculator”.
I have a medium sized Exchange 2010 Environment that I would like to upgrade to Exchange 2016.
The current Exchange 2010 design is based on an Active/Passive design with a Single DAG that is shared across the Mailbox servers. We have around 5500 mailboxes spread across 10 databases.
When I came to put all this detail into the “Exchange Server Role Requirements Calculator” it suggested I have
• 6 Servers in Active site
• 3 Servers in Passive site
I agree with the server design but were a bit surprised when it suggested I have 9 Database Availability Groups? Is this correct? Why can’t I have just one DAG like in my Exchange 2010 environment?
I can’t see your calculator spreadsheet so I have no idea why it has given you that output. It’s not unusual to get a weird result from the calc first time, it often takes some patience and persistence to fix errors. If you’re still stuck then I’d suggest posting to the Microsoft Tech Community or to the /r/exchangeserver sub-reddit where you can also provide screenshots and get some opinions from others.
Thank you for your reply Paul,
I have posted the question again here https://techcommunity.microsoft.com/t5/Exchange/Exchange-Server-Role-Requirements-Calculator-DAGs-required/m-p/147776#M1738
Finally, I think I know what the problem is – My SPECINT2006 value was way off – I downloaded this tool “Exchange Processor Query Tool”https://gallery.technet.microsoft.com/Exchange-Processor-Query-b06748a5 and it calculated my SPECINT2006 value to be 645. Now the Calculator works correctly and recommends 1 DAG 🙂
Very useful and Simple Explanation, Appreciated for your effort.
i have a problem and Doubt. Can you pls help..
I had a single EXCHANGE 2016 . suddenly TRANSPORT Service Stopped and either not starting or not Stopping, the status is “starting”. Tried to fix.. no way…. SO i installed a Second Server and The Mail Flow is OK now. Now for the External URLs for New Installation, can i keep the same as the First server ? or should i remove from the first server? i dont have a LB now..also can i use the Same SSL certificate Export from first server and Import in to Second Server?
SERVER 1 : EXTERNAL URL . XXX.XXXX.COM
INTERNAL URL XXXX.XXXX.LOCAL
SERVER 2 : EXTERNAL URL : ————-
INTERNAL URL : xxxx2.XXXXX.LOCAL
Your new server should use the same namespaces and certificate as the other server in that site.
Is failover cluster configuration required in exchange 2016 if 2 nod DAG available?
I don’t really understand your question.
Thanks for all your articles on Exchange, they are brilliant.
My questions is this, I know Exchange 2016 has a feature where the “mailbox” can follow the user. Example, if a user from the US travels to the UK I would want them to connect to their mailbox at the respective site. I’m trying to wrap my head around how to accomplish this with the DAG if the mailbox database can only be active at one site at a time.
Is this possible?
Exchange doesn’t have a feature where the mailbox can follow the user. The mailbox exists in a database, and that database can only have one active copy at a time. If the person is travelling temporarily, there’s nothing you can really do. If they’re moving permanently, you can move the mailbox to a database in that region if you really need to.
Hello Mr. Paul,
How to prevent the DAG offline when 2 node failure in “Node Majority” mode?
Hello Mr. Paul,
How to prevent the DAG offline when 2 node failure in “Node Majority” mode?
If one site goes down, i.e loss of internet connectivity, and unable to “inform” or connect to the witness server, this makes the DAG become offline for that site. How can you keep it up making it internally available for local users of that site to be able to access their mailbox?
A mailbox database can only have one active copy at a time. If you anticipate a scenario where a site will become isolated due to network failure and you need the users in that site to still be able to access their mailboxes, then you should place the File Share Witness in that site so that if the network fails the DAG node + FSW can still maintain quorum and keep the DAG online in that site.
Some documents claim that each DAG member could host 16 data base copies (1 active + 15 passive) .Also in Exchange Requirement Calculator they put limitation of choosing upto 15 “HA Database Copy Instances (Includes Active Copy) within DAG” but I see DAGs with so much more database copies on each member in real world.Could you please explain what is the reason ?
It sounds like you’re confusing the number of copies of a database with the number of database copies a DAG member can host.
A DAG has a maximum of 16 members, therefore the maximum number of copies of a database is 16.
A DAG member can host as many database copies as the edition of Exchange allows (5 for Standard edition, 100 for Enterprise edition).
You might find this article useful:
Sorry for the delayed response. We are looking for redundancy for CAS functionality in exchange 2016. Without any load balancer can we achieve this. Like DNS round robin method. Thanks in advance.
You can do it with a load balancer or with DNS round robin. There’s an example here (Exchange 2013 and 2016 are basically the same for this):
We are using single DAG with two members and edge subscribed. How can we point the records for this. Private and Public IP Configurations. Please. Below are the internal details.
I don’t understand your question. What are you trying to achieve?
Please guide me regarding DC -DR network configuration for exchange 2016. Currently i m using 10.50.10.0 in my DC site and 10.90.10.0 in my DR site. My question is that,
01. Can i use same network directly connected in both site (10.5.1.0)
02. I have must use different network (10.5.1.0-DC & 10.6.1.0-DR)
03. I need your best recommendation regarding Microsoft
Please response soon
Microsoft recommends using separate IP subnets for each site.
I have added a 4th DAG member at our DR site. I have included an IP from the DR subnet in “Database availability group IP addresses” but was just wondering if I need to add an additional DNS entry for the new DAG IP address?
Great Article Paul, I would like to know more about the local search instance ‘read from passive copy’ (came with Exch 2016 CU3), when you make a passive copy to be active. And if there are 5 servers in a DAG, and one is active, on the event of active copy server failed, what parameter DAG use to choose one passive copy to become active ? If you have already any article please give.
There’s a process called best copy and server selection that makes the decision.
Broad stroke recommended plan if I may: We have a (flaky) 2 site DAG on Ex2010. Main site is the office where all staff are located, remote site is a backup data centre. Sites connected by 100Mb VLAN.
We are moving to Ex2016 across the two sites with an Azure based Kemp load balancer.
I’m happy enough with the risk to roll back the Ex2010 estate to a single (clustered) server at the main site, so I’m thinking to do that then deploy Ex2016 as a single (clustered) server at the main site, migrate the single server over and remove Ex2010, then expand the Ex2016 estate to a DAG across the two sites with external client access coming in via the Azure Kemp load balancer. There’s a few new things to learn along the way so I’m cautious to not bite off more than I can chew in one go! Does that sound like the “easiest” approach, or do you have other recommendations?
I don’t know what a “single (clustered) server” is.
Apologies for being so brief – The HA cluster is obviously two (or more) servers with shared storage. The Exchange server is a VM on the cluster. So from an Exchange server point of view it’s just a single server, but from a hardware point of view HA is provided by the cluster. My description was supposed to show it was a single server, running in a cluster environment.
Hope that helps!
can we separate replication network with IP less DAG configuration ?? talking about exchange 2016
Yes, but the recommended practice is to just run a single DAG network and not create additional replication networks.
Thanks Paul, so in consideration to single point of failure of network what is recommendation to follow ?? i was thinking of NIC Teaming ..
NIC team is also not recommended.
I suggest you read The Preferred Architecture, which is guidance from Microsoft on how Exchange should be deployed for high availability. You’ll see that simplicity and predictable failure scenarios are key elements of a HA design. Things like NIC teaming and extra replication networks add more complexity.
Just as a hint: to my understanding, https://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx recommends a network separation in some scenarios:
“MAPI networks should be isolated from Replication networks: Windows network policies, Windows firewall policies, or router access control lists (ACLs) should be used to block traffic between the MAPI network and the Replication networks. This configuration is necessary to prevent network heartbeat cross talk.”
Do you have a question?
Hi Paul, looking for recommendation for 2 servers to be used at MBX servers with 1 Edge Transport server of lesser capability. All in the same datacenter.
The 2 mbx servers’ databases will be members of a DAG so that will provide High Availability.
When using the role requirements calculator, I can’t seem to get away from having to rely on backups and not relying instead on the Exchange Native Data Protection? Is this not possible with only 2 servers in one location?
Microsoft has specific recommendations for NDP, which includes a minimum of 4 DAG members across 2 sites.
You might find this useful as a starting point:
I am getting an error when adding the third server into the DAG.
A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: “AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired”. [Server: server.domain.domain.com]
I have 2 questions
1. i have 2 exchange servers and currently both are in the primary site and would like for the pother to be moved to the secondary , problem is that outlook users currently choose one or the other
i would like for outlook to choose only the primary server name and choose only the secondary when the primary is unreachable. How can this be effected.
2. Does the secondary and primary servers necessarily have to be in a different AD sites
1. You control where clients connect to via DNS or load balancing for the client access namespaces.
2. It’s not mandatory but it is recommended.
My scenario is similar to Aletheia’s.
As client access services (in Exchange 2016) only authenticate and proxy connections to back end services, would there be any performance issues for end users if I have a client access server in the primary site and another in the secondary (using DNS) over a slow link? All users are in the primary site.
That’s a question of whether your network performance is sufficient to handle the client connectivity. If you’re already stretching a DAG across two sites, hopefully there’s good bandwidth available.
Thanks for your prompt response.
I have a quick question regarding Exchange 2016 DAG DR site fail over. I currently have the following environment:
2 Datacenters (Production and DR)
3 Exchange 2016 CU1 Servers (2 in the Production datacenter, 1 in DR datacenter)
1 Witness server located in the Production datacenter (I know it’s not really doing anything because I have 3 Exchange servers in my DAG)
During a disaster scenario where my Production datacenter is completely down, will the DAG automatically switch over to DR or do I have to run the following commands:
Stop-DatabaseAvailabilityGroup DAG01 –MailboxServer Server1 –ConfigurationOnly”
Stop-DatabaseAvailabilityGroup DAG01 –MailboxServer Server2 –ConfigurationOnly”
Then from the Exchange 2016 Server in DR:
Restore-DatabaseAvailabilityGroup DAG01 –ActiveDirectorySite Datacenter-2
I have the same doubt, is it possible we can do datacenter switchover if the site DR has just one member dag and alternate witness? I’ve tried to do that but it couldn’t work because I’ve got quorum issue.
Yes, it’s possible if you follow Microsoft’s datacenter switchover guidance correctly.
The article is great, detailed and self explanatory…
Thanks for all the efforts…
Currently I have 2013 DAG,
1) 2 Servers Each having all roles installed on it.
2) I have barracuda Spam filter too.
3) I have pointed my mail.company.com and barracuda to DAG IP.. functioning flawlessly from past 2 years.
4) In case of a server failure the second server takes over automatically, without CAS, HW loadbalancer in picture
I have some queries..
Since exchange 2013 creates IP less DAG
1) Where will clients connect to?
2) What will happen to Clients… OWA & Outlook?
I am planning to upgrade my Ex2013 to 2016… a lot depends upon the answer to this..
Since exchange 2016 creates IP less DAG
We are running Active Directory windows 2008 and Microsoft exchange 2010 SP3 with standalone servers.
I am planning to Migrate the AD to windows 2012 and Exchange to 2016 .The Exchange will be in DAG.I am also Planning to add a new Active Directory and an Exchange server which will be a part of DAG in second Location as a DR approach.
Is it possible to migrate AD to 2012 and after Exchange to 2016,and configure DAG in DR site.How many total Witness server required.
Any Body Comments please
Your question is a bit confusing but I’ll try to answer it. I think what you’re saying about the “new Active Directory” is you plan to add a new AD domain controller to a second location. Yes, you can add an Exchange server to that second location as well, but it can’t be the same server that is also the domain controller, you’ll need to make them two separate servers.
Yes, you can configure a DAG using the two Exchange servers in each site. You’ll need one witness server, and it should be located in the primary datacenter.
What’s your opinion of dedicated replication NICs for 2016 Exchange? It used to be that was always recommended but with 2016 it’s not anymore? What is best practice in your opinion?
Its maybe a really stupid question but I can’t seem to get things working in our Lab…
Assuming I have three exchange server… one DB in a DAG over all three exchange servers.
Am i supposed to be able to shut down the server on which active copy of DB is running – should DAG failover the DB to one of the other “passive” servers?
I set up a DAG as described in your Blog, MapiDagNetwork is rep disabled and ReplicationDAGNetwork01 is enabled for replication.
Running Get-MailboxDatabaseCopyStatus shows DB status one mounted and others healthy… Exchange Server Health Check Report is green and everything seems to be ok.
To test if failover would work i found a website from Microsoft (https://officeignitelabs.cloudguides.com/Guides/Testing%20Database%20Availability%20Group%20Switchover%20and%20Failover.htm) telling me to stop the process named Microsoft.Exchange.Store.Worker on the server holding the active DB copy…
Outlook seemed to work fine, ecp connection wasn’t lost either and after refreshing the ecp I saw the active copy of DB has hopped to another Server. So everything seemed to work.
But… If I shut down the server with the active copy nothing works. ecp, owa, outlook everything loses its connection and doesn’t start up until that server is up and running again. The DB then still is on that server and didn’t change its active copy to another, running, server.
Maybe you have an advice?
As others have said your articles are an invaluable source of information, the go-to site for Exchange related matters.
We currently have Exchange 2010 SP3 RU12 configured in a cross-site DAG with a single client access server in its own CAS Array in each site. The two data centres are connected at 12mbit. All the databases in the secondary site are passive and only activated (manually) in the event the primary data centre is unavailable.
Our data centre situation is going to improve which includes much better network bandwidth to our secondary data centre. The data centres will be separated geographically but connected over dark fibre in the same subnet (AD site).
It looks like we will go with Exchange 2016 (now that all our third-party applications are supported, and the goal of using Exchange Online archives soonish), configure the DAG and perform mailbox moves to the new Exchange 2016 servers, giving us pretty much zero downtime for Email services during our data centre move.
We plan to split the databases 50/50, i.e. half active on one DAG member and the other half active on the other DAG member, automatic activation should one of the DAG members become unavailable. The complete opposite of how we are doing it today.
1) What is the behaviour of Exchange 2016 when it comes to accessing mailboxes? If I have a namespace e.g. outlook.company.com with an internal A record pointing to Exchange server 1, will Outlook use Exchange server 1 for its Autodiscover lookup and then connect the Outlook client to the Exchanger server on which the database is mounted or will Outlook use Exchange server 1 to access a mailbox which its database is mounted on Exchange server 2?
2) Without a hardware load-balancer in play (possibly in the near future), in the event site 1 is unavailable can I simply amend (small TTL) the internal DNS record of our namespace to the IP address of the other Exchange server?
Explains it nicely.
In your example of a two member DAG, with an FSW, if the FSW fails, the DAG will stay up, correct? If one DAG member and the FSW fail, then the DAG shuts down, correct?
FSW acts as a tie-breaker in a two member DAG. I shut down one of the Exchange servers and all is well!! There is simply a warning if another node or access to the FSW is lost the cluster will fail.
The quorum model is designed to be automatically adjusted:
A Node Majority quorum model is used for DAGs with an odd number of members.
A Node and File Share Majority quorum is used for DAGs with an even number of members.
Thanks Paul for the Good Explanation, I will try that.
I’m trying to deploy a two datacenter site resilient solution that can survive a wan failure. I have found Exchange 2010 documentation that says to create two four member DAGs. The goal is to have both sites operational if a network failure is preventing communication between the two sites. Do you know if this is still the model in Exchange 2016, or have their been changes in the architecture that no longer require two DAGs?
Yes, if you need two separate datacenters to be the “active” datacenter in a WAN failure so that they can serve different geographic regions, then two DAGs is still the solution in Exchange 2016.
What if you didn’t have this solution but only needed to have an automatic failover and run solely out of the secondary site if the primary location was offline? Right now I have a 3 node DAG (2 primary, 1 secondary) for Exchange 2010 but will be transitioning to 2016. My requirement is a more automatic failover solution and the ability to fully serve all users out of the secondary site (OWA/Autodiscovery). Would the 3 server situation remain?
If you want automatic site failover you need a third datacenter that can host the file share witness, and you need the primary and secondary datacenters to host an equal number of DAG members each.
What will happen in this case when link between first and second datacenter will down but links to third datacenter will remain for both datacenter? Will lead this to split brain situation eaven DAC mode configured in DAG?
The network design should allow the sites to continue communicating via the third site, if they can both reach it.
Thanks again for the comprehensive feedback.
Thanks Paul, yes we know, but we will test it thoroughly before implementing. The OWA won’t help us when the remote site is down for a couple of days. And yes it is going to be a nightmare, but we’ll give it a shot, without an MS product though.
Forgot to add: when we place the server off-site we have the problem that all ‘internal’ emails need to go offsite and back on-site again to be received. That way they won’t have communication when the site is cut-off the internet…. With the server on-site at least the local business can continue. Know it sounds crazy/rare but we have dozens of clients facing this issue…
If the remote site is down you lose sync between two replicas anyway. There’s no solution here that protects you from every failure scenario. At some point you’ll need to decide which parts of the service you’re willing to lose under certain failure scenarios. Otherwise you’re looking for a unicorn.
Well, let’s say we have a sync between onpremiseoffpremise DB (assume this is possible). MX comes in to offpremise, so when not on site emails will be received and also senders will get no bounce back.
On-site the people can still email between one and another and prepare emails to be send to the ‘outside’ world.
In theory this sounds better than having (with the downsides outlined above) one location where a Exchange environment exist.
Only thing is what ‘happens’ if the sync becomes available again between the two DB’s.
Whatever hypothetical sync product you’re looking for would have to reconcile a lot of change between the two sync partners any time the link was lost for a period of time. In fact, I imagine that if you did lose a link for a few days, the sheer volume of sync needed between the two copies to catch up again would saturate the link for several more days anyway, rendering it useless for normal connectivity.
Bottom line, an Exchange DAG won’t meet those requirements that you’ve spelled out.
This does not, by any means, create an active active Exchange server deployment right? So a mailbox of user X resides in a Exchange server deployment in location A within DB01 and simoultaniously in Exchange server deployment in location B withing a replication of DB01 (or even a DB02).
As far as i know an active active email server DB with Exchange is not possible, only HA right.
You can’t have a single mailbox active-active amongst two exchange servers wich replicate each others databases (correct me if i’m wrong).
You are correct.
“Active/Active” in Exchange DAGs doesn’t refer to having two copies of a mailbox active at the same time.
Thanks, hope it will come some day, for now we have to move away from Exchange because of some specific client requirements. We do really need the active-active database where a single mailbox can be active on both databases simultaneously.
I’ve never met a customer who required that, but I’m sure you’ve got your reasons.
Well, imagine a site with very limited , expensive and slow internet connectivity (satellite internet) which is high in latency and might drop out often.
When you are on-site (30-40 users) you have an exchange deployment there so emails sent between those people stay local and don’t use the limited and expensive bandwidth.
When leaving site (what happens often they work on rotation) they want/need email connectivety and they connect to the on-site server, via that very slow link, they also send/receive emails through that link.
This ‘hammers’ the sattelite connection and creates huge delays in email. Also when the connection is offline (which does happen quite often) there is no email connectivety at all.
So if an offsite Exchange deployment would exist and we have a sync between the on-site and off-site deployment of all boxes emails would only sync once.
We let all external emails go to the off-site deployment first and let it sync through with the on-site deployment.
Via DNS we resolve (on-site) to the local Exchange server and off-site automatically to the other (off-site) deployment.
You see the problem? This solution is not part of Exchange is it?
I’ve been looking at hybrid office 365 deployments but you need to transfer the mailbox. That is of course no option through that slow link.
Also when they go off-site for one day or a couple of hours this does not work.
Maybe you have another bright idea, but we are (Exchange wise) a bit out of options.
Thanks for your replies really appreciate it!
No, Exchange can’t do anything like that. I doubt that solution is really going to help you, to be honest. You’re trying to reduce client traffic over a slow link, but you’re going to replace it with replication/sync traffic anyway. One way or another, the bits need to cross the wire. And trying to maintain sync over an unreliable connection is going to be a nightmare. I predict a lot of data inconsistency issues with anything that tries to work like that over a bad network link.
Not knowing all the details of your situation, I would suggest that you put the server wherever the most people are located. If that is on-site, so be it. For anyone accessing email off-site, they should use the most lightweight connection option available, which is Outlook Web App (OWA), now called “Outlook on the web” in Exchange 2016.
Hi – Do I need to configure internal and external access URL’s for virtual directories when adding a second exchange 2016 server as part of DAG creation? Thanks!
Correction: Do i need two SSL certificates, one for each server or can i use the same SSL certificate for both servers.
One certificate is the recommended approach. But the certificate is not directly related to DAG functionality, it is for client access services, which also needs to be considered and planned properly in a HA deployment.
New to DAG to implement it with 2016 migrating from 2010 single server setup.
Looking to implement a DAG for exchange 2016. Do i need to have two certificates for each server?
good description of the process. I would like to know if the witness server requires any exchange components installed and if it requires an exchange license.
No Exchange components, and no Exchange license. It’s just a Windows Server with a file share.