Bom dia my friends!
Yesterday we configured the CNO to support our DAG and in Today’s post we are going to create the DAG using EAC. To make sure that we are on the same page here are the key features of my lab:
- 2 Domain Controllers running Windows Server 2012 RTM; my forest and domain were configured to Windows Server 2012
- 2 Exchange Server 2013 RTM deployed with Client Access role
- 2 Exchange Server 2013 RTM deployed with Mailbox role and a key components:
- 2 Network adapters (one for LAN and another one for replication); The DNS registration is disabled on the replication adapter, just in case I configured 255.255.255.252 subnet to allow only 2 hosts.
- Drive M: on both servers where we are going to configure our future mailbox databases
The DAG configuration using EAC can be found when we click on servers, and then database availability groups and on that place we are going to find all DAGs. Let’s create our first one, shall we?
The first step is to click on the Add button (+ icon) and on the new page, let’s use the CNO that we created yesterday (MVDDAG) and we can define which server will be the witness server (the recommendation is to use another Exchange Server that won’t be part of the DAG to keep all exchange administration on servers where the mail administrator has jurisdiction ). We can also define the path for the File Share witnes (by default is C:DAGFileShareWitness) or leave it blank and the default value will be used.
Finally, let’s define an IP to be used for the DAG and then click on Save.
That’s all to create a DAG, and as soon as we start adding members then this IP and the cluster configuration itself will be deployed automatically to the new members (that is our topic for tomorrow!).