On my last blog, I had a talk about DAG (Database Availability Group) on Exchange 2016. Fortunately, I had smooth configuration but luck doesn’t go every day like that. Here is one of the issue you might face during the configuration of DAG and also I have posted resolution on it.
DAG
DAG Configuration on Exchange 2016
As I have already explained on my previous blog, that Email has become quite critical service within an organization. Service down of an email might bring the business down. Hence every organization would like to configure HA (High Availability) of Email Services. Since there has been restructure of an Architecture of Exchange server 2016, it has been different from the previous Exchange Servers.
In previous version of Exchange server, we use to configure 4 (Four) boxes for HA. Which consist of 2 (Two) CAS servers and 2(Two) Mailbox servers. For CAS Servers, we use to do Network Load Balancing using either Windows Network Load Balancer (cheap solution) or Hardware Load Balancer (Recommended Solution). And for the mailbox servers, we use to configure DAG (Database Availability Group) which internally does Failover cluster between the databases of mailbox servers.
Aerrow 