How to Create\Configure DAG in Exchange 2013

I have a test lab which is good enough to test the Database Availability Group configuration in Exchange Server 2013 and I tried it on last weekend. After lot of errors, I successfully created Database Availability Group in Exchange 2013. Below are the steps that I followed to successfully create/configure Database Availability Group in Exchange Server 2013

Steps that I followed

• Prepare the Exchange 2013 environment to create DAG


• Creating the Database Availability Group


• Adding the Mailbox Servers as member of the DAG


• Adding the Mailbox Database Copies to the passive node

Prepare the Exchange 2013 environment to create DAG


Preparing the Exchange 2013 to configure DAG includes the following Steps

• Exchange Servers: You should have two Mailbox Servers installed with Exchange Server 2013. If it is an exchange 2013 standard edition, both the member server has to be standard edition servers.


• FSW: File Share Witness server has to be different server and it should not be a member of DAG.


• DC & GC: Windows Server 2003 Sp2 or later


• Domain and Forest Functional Level: Windows Server 2003 or later

My Test Lab: I have the below servers in my test environment

• EXCH2013-DC – Domain Controller running on Windows Server 2012


• CHENNAI-01 – Mailbox & Client Access Server Role installed together running on Windows Server 2012 datacentre edition


• CHENNAI-02 – Mailbox & Client Access Server Role installed together running on Windows Server 2012 datacentre edition


• CHENNAI-FS1 – File server running on Windows Server 2012


• Domain Functional Level: Windows Server 2008

Below figure shows the Exchange 2013 servers that are installed in my test lab



Placing the File Share Witness in Exchange 2013 DAG


The Witness server is a required property for all DAGs, but it is used only when the DAG contains an even number of members. FSW can be configured on Exchange 2013 Client Access Server or any other file server running on Windows Server 2003 Sp2 or later

If we are configuring the file server as a File Share Witness, then the Exchange Trusted Subsystem has to be member of the local administrators group on the File server. If it not configured the error message "The Exchange Trusted Subsystem is not a member of the local Administrators groups on specified witness server" will appear as shown below



Note: You may get the same error after making the Exchange Trusted Subsystem as a member of the local administrators group on the File server. To fix it, restart the File Server once.

To add the Exchange Trusted Subsystem, open Computer Management Console -> Local Users and Groups -> Groups -> Administrators -> Members



Creating the Database Availability Group


To Create New Database Availability Group, Exchange Admin center -> Servers -> Database Availability Groups -> Click on the + symbol to create new DAG



Below screen appears… enter the DAG name, Witness Server FQDN name, Witness Directory and the IP address of the DAG



Below shows the confirmation of DAG creation



Note: You may get error while creating Database Availability Group on Windows Server 2012, to resolve the issue... you have to Pre-stage the Cluster Network Object by following the link here

Adding Mailbox Servers as member of the DAG


To add the Mailbox Servers as member of DAG, open Exchange Admin Center -> Servers -> Database Availability Groups -> select the Database Availability Group -> Click on the Manage DAG membership option



On the new opened window, click on the + symbol to add the member servers



Add the servers that are going to be member of the DAG and click on the Save option





Below shows the adding DAG members task



Below shows the completion of adding member servers to Database Availability Groups





Adding the Mailbox Database Copies to the passive node


To add the Database copy to the passive node, Click on Exchange Admin Center -> Server -> Databases -> Select the Database -> Click on … and select Add Mailbox database Copy



On the Opened Window, enter the details and click save



You can test the Mailbox Database copy status using "Get-MailboxDatabaseCopyStatus" commandlet.

Let us know if you are facing any issue in creating\configuring database availability group in exchange server 2013.