How to create Exchange 2013 DAG and Test DAG Failover

December 23, 2014 at 12:27 pm 1 comment

Dear Folks

Today I decided to write a post explaining Exchange 2013 DAG Switchover/Switchback and Failover/Failback because I could not find a proper  or an consolidated article in the Internet which explains  the required steps to install and test  the DAG.

This article will be divided in to 3 sections

Step 1 – Installation of Exchange Prerequisites and Exchange Installation
Step 2 – DAG creation
Step 3 – Testing (Switchover/Switchback and Failover/Failback)

Environment
1 DC (Windows 2012 R2 OS, Domain: Test.local)
2 Exchange Servers(Windows 2012 R2 OS, Exchange 2013 CU6)

Step 1 – Installation of Exchange Prerequisites and Exchange Installation

In this series we will walk you through the process of performing a clean installation of Exchange 2013 in single server.(Windows OS installation will not be covered)

> Begin with Installing the AD DS and AD LDS Roles to prepare the AD forest for the Exchange 2013 deployment.

1-prerequisite_ad_roles

> Thereafter open an elevated command prompt run the prepare schema command

4-prepareschema  5-prepareschema_success

> Then start with the AD Preparation in this you need to mention the Exchange Server Organization Name

6-preparead7-preparead_success

> Now you could prepare the domain.

8-preparedomain  9-preparedomain_success

>  We need to install the below prerequisite based on exchange roles that will be installed since my deployment is single server role (cas and mbox together)

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation ( For other roles please refer Technet Article http://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx )

10-exchange_prerequisites  10-exchange_prerequisites_success

>  Next we install the below mentioned components in the mentioned order as

1.Net Framework 4.5.2 (Only for CU7 , In case CU6 the required .NET Framework is pre installed)

2.Microsoft Unified Communication Managed API 4.0,Core Runtime 64-bit

 

11-ucma_filterpack_sp

>  Finally begin the Exchange Installation  by running setup.exe and follow the screen (selected option may vary based on your environment requirements) below are some of the customized options as per my LAB

16-setup_screen_5  18-setup_screen_7

 

Step 2 – DAG creation

Now we have installed the Exchange Servers. We will begin with the DAG creation.

> As a prerequisite the Exchange Installation or the Database and Log location should not to be identical in my case it was not

hence I need to move the Database and Log Files.

20-moving_db

> Thereafter we need to pre create the CNO (Cluster Name Object) when we deploy DAG on Windows 2012 or Windows 2012 R2

 1) Create a new computer object via Active Directory Users and Computer Snap-in

21-prestaging_cno

 2) Disable the Computer Account created above and Press ” Yes” on the Prompt.

21-prestaging_cno_1  21-prestaging_cno_2

3)  Enable “Advanced Features”

21-prestaging_cno_3

4) Right Click the Computer Object Created  and add one of the Exchange Mailbox server and grant Full control

21-prestaging_cno_4

5) Add the File Witness Server in my case the Domain Controller in Exchange Trusted Sub System Group

22-new_dag_0

6) Add the Exchange Trust Subsystem group on the Local Administrator Group of the File Witness Server.

22-new_dag_0_1

Everything is done now we will begin with the DAG creation

7) We will create a DAG with the below parameteres

DAG Name : – DAG

IP Address  :- 192.168.252.131

FSW Server : dc.test.local

22-new_dag_1

NOTE:- I forgot the step 6 in my LAB and the FSW was not created , hence   I need to re set the FSW property on my DAG after completing the Step6

22-new_dag_223-verify_database_log_path

8) Add the Mailbox Servers to the DAG.

22-new_dag_3

9) Verify the Cluster Resource to confirm whether the above commands are executed correctly and the required cluster  resources has been created.

22-verify_cluster_resource

10) Now we are going to make the Database Copies ,hence check the Database and Log Path on the Exchange Server.

23-verify_database_log_path

11) Add the First Copy

24-add_databse_copy

12) Verify the Database Copy Status and repeat the steps for the other databases.

(If you notice any status other the Healthy you could give some time or simply restart the Information Store Service.)

24-verify_database_copy_status

 

Step 3 – Testing (Switchover/Switchback and Failover/Failback)

1) Now we have successfully created the DAG we will  go through the testing .( While testing I prefer if you could open an E-Mail Client to test the email flow between 2 accounts)

We will perform a database switchover which is a planned activity and can be done via ECP , Hence login to ECP –> Servers –> Databases

Select the passive copy of the database on the Exchange2 server and click on activate it.

26_database_switchover

Test the e-mail flow .

2) Now we will test the automatic service recovery a beautiful feature of DAG.

In the below snapshot we will stop the IISAdmin service  and confirm that Exchange will restart the service automatically

26_service_recovery

3) Now we will perform a  Failover which is an unplanned activity,In order to do this we will crash or stop the process Microsoft.Exchange.Store.Worker

on theExchange2 Server

26_failover_test

Once it done you will notice on the ECP that the Passive Database is activated automatically on the Exchange1 Server and now you could test the e-mail flow.

26_failover_test_database_activated_on_other_node

 

Done.

 

 

 

 

Advertisements

Entry filed under: Exchange and O365. Tags: , , , , , , , , .

Exchange 2013 GRT Fails with Symantec Backup Exec 2014 SP1 How to perform a Local Mailbox Move Request on Exchange 2013

1 Comment Add your own

  • 1. Helga Dullen  |  August 22, 2018 at 10:52 am

    I think you have noted some very interesting details , thankyou for the post.

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Trackback this post  |  Subscribe to the comments via RSS Feed


Archives

Categories

Follow Hope you like it.. on WordPress.com

Blog Stats

  • 17,533 hits

%d bloggers like this: