Tuesday, May 28, 2013

Exchange 2013 – Database Availability Groups



I got opportunity to build Database Availability Group configuration in Exchange Server 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: At least you 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
  • Corp.com-DC – Domain Controller running on Windows Server 2012
  • MX1 – Mailbox & Client Access Server Role installed together running on Windows Server 2012
  • MX2 – Mailbox & Client Access Server Role installed together running on Windows Server 2012
  • Domain Functional Level: Windows Server 2008
  • FSW is DC itself.

·         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
·         Sometime 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 enter the DAG name, Witness Server FQDN name, Witness Directory and the IP address of the DAG

Below  screen you can see the DAG is created name DAG01.

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

In below screen we added both mailbox server MX1 & MX2.

Once added mailbox server on DAG click on ok 

Taking a quick look at the full error, I realized there was an “Access is denied” error. More specifically the error stated, “Error: Cluster API ‘”CreateCluster() failed with 0×5. Error: Access is denied”. Double checked the Exchange Trusted Subsystem group membership and all three Exchange servers were in fact present.

To set the proper permissions on the CNO object that was already created in the attempt at forming the dag, we need to launch “Active Directory Users and Computers“, and click “View“, then “Advanced Features“. Locate the CNO (cluster network object), 

After assigning the proper privilege got successful. 

Now you can the DAG01 with two members.

Now you can also manage the DAG network 

For replication network


For MAPI network

Finally click on ok.

No comments:

Post a Comment