How can I create a DAG in Exchange 2013?

I have an Exchange 2007 server, two Exchange 2013 hybrid servers with mailbox, HT and CAS role installed and I have migrated most of my mailboxes from Exchange 2007 to Office 365 Exchange Online.
Everything works great but now I have to move the remaining mailboxes on exchange 2007, which for various reasons must remain on-premise, to the Exchange 2013 hybrid servers and then decommission my Exchange 2007 Exchange server. I am going to build a third Exchange 2013 hybrid server so I can configure a DAG.

I have the instructions on how to setup an IP-less DAG.

What should I be aware of during this process?
Are there any gotchas I should be aware of?
Aside from the DAG setup, are there any changes I need to make to my current Exchange 2013 hybrid server install?

Thank you.
Who is Participating?

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

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.

Will SzymkowskiSenior Solution ArchitectCommented:
When you have DAG's setup for mailbox servers you need to ensure that your Paths for Logs and Databases are consistent on all of your servers in the DAG. When you enable a passive copy on another mailbox database in the DAG it will use the same path that it uses on the Active Server.

You also need to make sure that you create the CNO (cluster name object) in Active Directory first before you proceed creating the DAG.

I would also highly recommend making sure that you have a "Production" NIC and a "Replication" NIC. This is also recommneded by Microsoft as well. You do this so that when your databases ship transaction logs to other DAG members it runs on its own network and does not saturate the production network.

This comes in to play when you are working with large database. If you ever have to reseed a 200GB database to another DAG member it will slow down your production network considerably until the copy process is completed.

Using a Replication network mitigates this disruption.

The Production network is always used as a backup to "keep the lights on" but Replication network should always be primary.

Aside from that Exchange 2013 is pretty straightforward when creating DAG's.


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
cyberleo2000Author Commented:
thank you for the feedback
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

From novice to tech pro — start learning today.