How to create a Database Availability Group in Exchange 2013

Posted on December 4, 2012 | Category :DAG, Exchange 2013 | 6 Comments

Well, Creating Database Availability Group (DAG) Became much more simpler,

But configuring it properly is the best part to have it efficiently working.
So lets see how to create a 2 node DAG ,

NOTE **Am not going to Describe about load balancing for Client Connectivity in this blog

I will describe my environment now

I have 2 AD sites

Every AD site has Exchange Servers

image

image

========================================================
First we will prepare the Environment for the DAG
———————————————————————————-
I will have my Primary LAN . Will add a Replication LAN ,for my DAG replication for all the nodes which am planning to add in DAG

image

Verify my NIC binding are Correct

Advanced – Advanced Settings

image

1.Primary Network

2.Replication Network

image

Make Sure they are in a Different Class of IP

Primary Network –

image

Replication Network –

*No Default Gateway

*No DNS Servers Set

*Add a persistent Route for all the nodes with the Replication NIC’s

Replication NICs should ping with other replication NIC’s – So that DAG replication will happen through these NIC’s

Port Used : 64327

image

Now there is no Single point of failure on my LAN
If my replication network fails it can failover to the production network. vice versa.

When creating a DAG with Mailbox servers running Windows Server 2012 in an Active Directory environment with Windows Server 2008 R2 directory servers, you must pre-stage the cluster network object before adding members to the DAG. For detailed steps, see Pre-Stage the Cluster Network Object for a Database Availability Group.

See

http://technet.microsoft.com/en-us/library/dd351172.aspx

Lets See How to pre stage a Cluster CNO object.

Open ADUC – New Computer Account

image

Enter the DAG Name

image

Disable the Account

image 

Give Full Control for Exchange Trusted Subsystems

image

Add the First Node Computer account and Give Full Control

Note -  Choose Object types to Select Computer Accounts

image

image

Apply the Permissions

Reference link -

Pre-Stage the Cluster Network Object for a Database Availability Group

==========================================================================
Now we will  Create a DAG ,

 

Login to EAC –Servers – Database Availability Groups – Choose New

image

 

Specify

* DAG name

* Witness Server Name

* Witness Location

Add Two DAG ips’ (Static IP for the DAG )

1 for Primary Site

1 for DR site

if you have different subnet or different class of ip on either Sites.
Have Two IP address for the DAG so that DAG resource can be online while failover on either sites
If you have only one Subnet , then you can have only one Ip address for the DAG

image
Now my DAG Configuration is Ready

Add members to it.

Choose Manage DAG Membership

image

image

Adding the members

image

Now you can add the other DAG memberwhere it should get added without any issues.

image

Great !! Now your DAG is ready !!

 

See

How to Add Database Copies in Exchange 2013

Satheshwaran Manoharan

Exchange MVP , Publisher of CareExchange.in
I have been supporting/Deploying/Designing Microsoft Exchange for some years . If you any Questions ?. Please share you thoughts via Comments.

LinkedIn Google+ Skype 

Comments 6

  1. Amit Reply
    13/01/25

    Excellent

  2. Leo Reply
    13/03/27

    Hi Sathesh,

    Thanks for your article. I have a question here…By default it’s recommended to enable IPV6 for Exchange 2013, if we disable this there is an issue with the starting transport service.

    I noticed while installing the DAG IPV6 is disabled for MAPI (Primary) network, will this will create an issue.

    • 13/03/27

      Database availability group member
      Ipv6 Supported = Yes, You need not to disable it, It should work without any problems

      Static IPv6 addresses are supported by Windows Server 2008 and the Cluster service. However, using static IPv6 addresses goes against best practices. Exchange 2013 on Windows Server 2008 doesn’t support the configuration of static IPv6 addresses during setup.
      Failover clusters support Intra-site Automatic Tunnel Addressing Protocol (ISATAP). They support only IPv6 addresses that allow for dynamic registration in DNS. Link local addresses can’t be used in a cluster

      http://technet.microsoft.com/en-in/library/gg144561(v=exchg.150).aspx#DisEna

  3. 14/03/12

    Great guide and tutorial. I just have one quick question. Is it possible to create DAG without third server that will act as witness server? Currently, we have installed two Exchange Server 2013 on Windows 2008 R2 Enterprise SP1 on two HP Proliant Servers. The AD on the Live Server is being replicated to the AD on the Backup Exchange. We want to configure DAG to replicate the mailbox database of the Live Server to the Backup Server. I have read some tutorials that it is mandatory to have 3rd server that will act as Witness Server because the DAG members should not be a witness server.

    • 14/03/20

      First Exchange on DC is not a Good thing.
      Having witness on Exchange server is not possible
      in a two node dag . without witness . Its not going to fail over .when one node goes down.

Leave a Reply

Your email address will not be published.

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Current day month ye@r *