Questions on IP and IP-less DAG
Dear Experts, I'm studying the DAG of Exchange server. Is my understanding correct?
Assume that our environment is having:
- 1 AD server 2012R2 (IP address: A.B.C.30 / 24)
- 1 Exchange server 2016, running on address: mx1.domain.com (IP address: A.B.C.21 / 24)
- 1 witness server 2012R2 (IP: A.B.C.25 / 24)
and now we are adding the 2nd Exchange server (IP: A.B.C.22 / 24) to create a new DAG.
1. With IP-less DAG, is the access domain still separated? For example: when MX1 goes down, users still need to change their web browser to mx2.domain.com to access the mailbox? Cannot use mx1.domain.com anymore? Is there any solution from public DNS?
2. With IP-DAG, we will have a shared name to use between 2 Exchange servers, for example mail.domain.com? Then when MX1 or MX2 goes down, users can use mail.domain.com normally?
3. What are the pros and cons of IP and IP-less DAG?
Many thanks in advance!
ASKER
Today I removed the IP-less DAG and add a new one DAG01.domain.com with IP - A.B.C.23; I also defined the A record of DAG01 and MAIL on AD/DNS; so that users can access owa via DAG01.domain.com or MAIL.domain.com
When I tested the DAG's operations, I found that the failover process is quite slow. For example when 2 nodes are running and MX1 is cluster owner, then I turned off the MX1 => it took about 5 mins for Exchange to work properly again (MX2 now is cluster owner) although DAG01 cluster realized it immediately (and changed its owner to MX2).
So how can I improve failover performance? fasten the process? Thanks!
I have recommended this question be closed as follows:
Split:
-- 'Hayes Jupe' (https:#a43331362)
-- 'Amit' (https:#a43331596)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
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.
TRUSTED BY
ASKER
how can I configure a shared name for both MX1 and MX2, for example: mail.domain.com?
And I have to configure each other's send and received connectors just like standalone method?