Solved

Setup DAG in Existing Exchange 2013 Environment

Posted on 2015-02-05
2
1,354 Views
Last Modified: 2015-02-06
Hi,

We currently have Exchange 2013 CU7 running on a single server with Hub Transport, Client Access and Mailbox roles.

The server is running Windows 2012 R2 Standard.

This server has mailboxes on it.

I was wondering how easy it would be to introduce another Exchange 2013 server and setup a DAG?

Could I install Exchange 2013 CU7 on another server, setup Failover Clustering on the existing and new server and then create the DAG?

Can the existing mailboxes remain on the existing server whilst this happens or would I have to setup the new server, move the mailboxes to it and then reconfigure the old server to be part of the DAG?

Also can the Hub Transport and Client Access roles remain on the existing server we have?  Also can I move these?

Thanks
0
Comment
Question by:Bolton09
2 Comments
 
LVL 3

Assisted Solution

by:Bahloul
Bahloul earned 250 total points
ID: 40590846
Hi,

see the blow links for DAG setup :-

http://goo.gl/y5kkv1
http://goo.gl/cYqfJw

you don't need to move theses boxes just add the new server and the replication will complete every thing.

Bahloul.
0
 
LVL 24

Accepted Solution

by:
VB ITS earned 250 total points
ID: 40590866
I was wondering how easy it would be to introduce another Exchange 2013 server and setup a DAG?
Honestly, it's ridiculously easy as long as you've met all the requirements.

- DAG members must be running the same version of Windows (i.e. 2012 R2 in your case)
- Exchange 2013 SP1 is required if Exchange is installed on 2012 R2 servers (you have CU7 which is fine as SP1 is in effect from CU4)
- The path to the database and log files must be the same on both DAG members
- You will need to specify a separate server as your File Share Witness (FSW) for the DAG as you can't use a DAG member as the witness server. See this article to set up the FSW prerequisites on another server in your environment: http://exchangeserverpro.com/using-a-non-exchange-server-as-an-exchange-2013-dag-file-share-witness/

More information on DAG requirements can be found here: https://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
Please ensure you take the time to read the entire article to avoid any potential issues.

Could I install Exchange 2013 CU7 on another server, setup Failover Clustering on the existing and new server and then create the DAG?
There's no need to install the Failover Clustering role, Exchange will do this for you when you create the DAG.

Can the existing mailboxes remain on the existing server whilst this happens or would I have to setup the new server, move the mailboxes to it and then reconfigure the old server to be part of the DAG?
Existing mailboxes remain on the current server, you don't need to move them. When you create the DAG, you then need to add a database copy to the second server so it can seed a copy of the database to the passive DAG member.

Also can the Hub Transport and Client Access roles remain on the existing server we have?  Also can I move these?
Exchange 2013 no longer has the Hub Transport role. Microsoft have instead consolidated it into both the Client Access Server and Mailbox roles.

With that being said, you don't need to move the CAS role to the new server. You can opt to install the CAS role on the second Exchange server if you want but you'll need to employ a VIP with round robin DNS or use a hardware load balancer (recommended method) for CAS redundancy. This is probably more suited for a separate question on EE though as there are numerous options out there to achieve this. For now your second Exchange server only needs the Mailbox role if your primary goal is to set up a DAG.

I highly recommend you have a read of Paul Cunningham's series of articles on exchangeserverpro.com to get a better understanding of the process to set up a DAG. I know it helped me out immensely when I first started out:
http://exchangeserverpro.com/exchange-server-2013-database-availability-groups/
http://exchangeserverpro.com/installing-an-exchange-server-2013-database-availability-group/
http://exchangeserverpro.com/exchange-2013-dag-database-copies/
0

Featured Post

Networking for the Cloud Era

Join Microsoft and Riverbed for a discussion and demonstration of enhancements to SteelConnect:
-One-click orchestration and cloud connectivity in Azure environments
-Tight integration of SD-WAN and WAN optimization capabilities
-Scalability and resiliency equal to a data center

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is my first article on Expert Exchange on the Manual Method of Exporting Office 365 Mailboxes to PST format by using the eDiscovery mechanism of Office. Hope you will enjoy the article.
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
Internet Business Fax to Email Made Easy - With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question