Lets get started, as we all know that Exchange Server 2013 RTM has been released for public few months ago.

Today we are going to Create and Configure Database Availability Group (DAG) in Exchange Server 2013 RTM running on Windows Server 2012.

LAB Environment:

Login to EAC (Exchange Admin Center) with Administrator rights. Click on Servers in the left pane, click on Database Availability Groups and Click on + sign to create the DAG.

Now specify the name of the DAG, File Share Witness Server and Witness Directory. In my case I am using Exchange Server 2007 as FSW Server and Witness Directory. We will define the DAG IP Address as well.

Click on Save you will get the below warning message, which you can ignore. This warning message has been there with DAG since exchange server 2010 days and Microsoft has failed to fix the issue till date.

In EAC now we will see the DAG01 object. DAG is nothing but an empty object in the active directory, if you check the Adsiedit.msc for DAG you will see nothing in it, as we haven't added any member server in it.

As we have DAG created and we will now add the member servers into the DAG. Click on Manage Member Servers and follow the instructions.

Click on + sign to add the servers.

Select the servers you want to add it as a member of the DAG and click on add button.

Click on Save and after you click on Save, it will install Windows Failover Clustering Components on the member servers and configure the cluster.

We have now added the member server in the DAG successfully, now it's time Add-MailboxDatabaseCopy from One (Active) Server to another (Passive). In my case E2K13 is the Active Server and MBXCAS is Passive Server.

We can only use EMS (Exchange Management Shell) to Add MailboxDatabaseCopy. We cannot use EAC to Add the MailboxDatabaseCopy. In Exchange 2010 RTM we had the same situation. We had only EMS option to add the MailboxDatabaseCopy.

After Add-MailboxDatabaseCopy completed successfully, lets check the status of the Database by running the command Get-MailboxDatabaseCopyStatus and the output of the command and EAC should be as shown in the below image.

Last but not the least check the replication health by running the Test-ReplicationHealth and Get-DatabaseAvailabilityGroupNetwork | fl.

I hope it helps.