SOLVED

Best method to add a dag

Brass Contributor

HI,
I have a question to ask.
I currently have an exchange 2016 cu23 with the latest security patches installed.
Now to guarantee continuity of service I want to install a second exchange.
In this way I will be able to configure a DAG to have redundancy at the mailbox level and I will use a kemp balancer for the redundancy and balancing of CAS traffic.
I would proceed like this:
-Installation and configuration of the second Exchange server
-Installation and configuration of the Dag. At this point I would have the redundancy of the mailboxes but not yet the one at the CAS level but in any case my clients can connect without problems with Outlook.
-Kemp installation and configuration
Or it would be better:
-Kemp installation and configuration
-Installation and configuration of the second Exchange server
-Installation and configuration of the Dag
Which method is better, the first or the second?

 

Thank you

 

Greetings

4 Replies
There's no real better or worse way...just whatever way you think would be best for your organisation or the way you would prefer to do it. Either way you won't have full redundancy until all the steps are completed. Hopefully you've read the Plan and Deploy Exchange high availability Learn pages to make sure your configuration will provide the HA level you need.
best response confirmed by pazzoide76 (Brass Contributor)
Solution

@pazzoide76 First Ensure that you have proper backups before making any major changes. Both approaches are valid, with Option 1, you can focus on mailbox redundancy first, ensuring that even if the CAS isn't load balanced initially, mailbox databases are redundant. Clients can connect without issues during the process, even before CAS redundancy is implemented. For Option 2, CAS traffic is load balanced earlier in the process, potentially providing better performance and redundancy for client access. This is beneficial if your environment has a high dependency on CAS services. Check this article for more insight - https://dzone.com/articles/how-to-manage-database-availability-groupsdag-in-e

Please Note: Since the web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

Thank you
Thank you
1 best response

Accepted Solutions
best response confirmed by pazzoide76 (Brass Contributor)
Solution

@pazzoide76 First Ensure that you have proper backups before making any major changes. Both approaches are valid, with Option 1, you can focus on mailbox redundancy first, ensuring that even if the CAS isn't load balanced initially, mailbox databases are redundant. Clients can connect without issues during the process, even before CAS redundancy is implemented. For Option 2, CAS traffic is load balanced earlier in the process, potentially providing better performance and redundancy for client access. This is beneficial if your environment has a high dependency on CAS services. Check this article for more insight - https://dzone.com/articles/how-to-manage-database-availability-groupsdag-in-e

Please Note: Since the web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

View solution in original post