Exchange 2016 DAG in Hybrid setup

Hi, I currently have a single exchange 2016 server with a hybrid connection to office 365.

We only use O365 for exchange protection and archives. All mailboxes are stored internally.

I use a split DNS with a certificate mail.domain.com

I am looking to add a second exchange server in a DAG so that maintenance can be performed on the primary server without any down time.

Looking for a bit of advice about how people would set up a DAG in a hybrid scenario.

I would presume I would set the DAG up internally with an IP Address, change mail.domain.com to point to that IP address.

Make sure I have the cert installed on both exchange servers.

Run the hybrid installation again to add both exchange servers to 365? Or can I only have the one connecting for the hybrid?

Am I correct with how I think I need to set up? Would I need to make any other changes etc?

Any advice is appreciated :)
LVL 6
CaptainGibletsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
Do not point mail.domain.com IP to DAG virtual IP

DAG cannot help you to connect clients to Exchange CAS component

mail.domain.com should remain pointed to Exchange server primary NIC

There is nothing changed for DAG setup in hybrid

U do need two network cards on each exch 2016 server and then form DAG and provide one VIP to DAG, infact you don't need any DAG VIP, you can create IP Less DAG

Hybrid will remain connected to both Exchange 2016 server as long as mail.domain.com pointing to both exch servers.
No special action is required for that
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CaptainGibletsAuthor Commented:
So I just create the DAG without an IP

Create a second A record that points mail.domain.com to the second exchange server as well.

But if the primary server goes down, clients still wont be able to connect through ActiveSync?
0
MaheshArchitectCommented:
have you changed active sync virtual directory on 2nd server to point to mail.domain.com?

If yes, please wait sometime to replicate mail.domain.com dns entry and then check
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

CaptainGibletsAuthor Commented:
I haven't installed the second server yet. I am trying to make sure I know exactly what I am doing before doing any installation.

Would changing the AS VD to mail.domain.com allow users to connect to the second server if the first was down?
0
MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Hi CaptainGiblets,
Make sure MSR proxy enabled on both servers.
Get-WebServicesVirtualDirectory | fl server,mrs*

Open in new window

0
MaheshArchitectCommented:
OK
I thought you have created 2nd server

mail.domain.com should point to both exchange servers
you do need two host records (mail.domain.com) with internal and external dns pointing to both server Ips
also make sure all virtual directories on both servers and autodiscover SCP should point to mail.domain.com
lastly as MAS pointed out, enable MRS proxy on both servers which is responsible for mailbox movement back and forth (OnPrem to cloud and vice versa)
1
MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
As commented by Mahesh do not use DAG IP (for mail.domain.com).  Just create 2 A records with your common name (e.g.mail.domain.com) points to two IPs which is DNS RoundRobin. i.e. Load balance the traffic between servers.
0
CaptainGibletsAuthor Commented:
Its now configured and working, thanks for all your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.