Exchange 2019: IPLess DAG

Exchange 2019 DAG Blog

Exchange 2019 is following Exchange 2013 and 2016 for Database clustering model and still living with DAG. In this blog I am sharing the steps to create DAG.

Check the following Exchange links before you move forward.

Prerequisite: https://laexugfoundation.org/prabhat/2019/12/e2019prereq

PrepareAD: https://laexugfoundation.org/prabhat/2019/12/e2019preparead

Installation: https://laexugfoundation.org/prabhat/2019/12/e2019unattendedinstall

My Setup:

-Operating system is Windows Server 2019

-Exchange is Exchange 2019 Cumulative Update 3

Steps:

  • Add “Exchange Trusted Subsystem” active directory group to the local administrators group of the “File share witness” member server. In case you are going to use domain controller, you need to add “Exchange Trusted Subsystem” group to domain administrators group.
  • Open ECP on Exchange 2019 server by opening following URL and login

https:\\localhost\ECP

  • Click on Servers à Database Availability Group

    Point to be noted: “Unified Messaging” is Gone and I don’t have SSL cert right now.


  • Click on + sign to create new DAG and Fill the following properties

    Database Availability Group Name

    Witness server

    Witness directory

    Database Availability Group IP Address: 255.255.255.255 then click +

    Click save.


    But we are focusing on command-based setup so we should try the following PowerShell command

    Run the below mentioned command from the Exchange Management shell

    New-DatabaseAvailabilityGroup -Name DAGName -DatabaseAvailabilityGroupIPAddresses ([System.Net.IPAddress]::None) -WitnessServer WitnessServerName –WitnessDirectory “Path of witness Directory

    New-DatabaseAvailabilityGroup -Name DAG01 -DatabaseAvailabilityGroupIPAddresses ([System.Net.IPAddress]::None) -WitnessServer WITNESS.exchange2019.com –WitnessDirectory C:\DAG01FSW


  • Now DAG will be created but addition of the servers is not done.
  • To add the servers, click on sign then click on + sign. In the select server select one server, click add then click ok.


    Or

    ADD the server by running the following command from Exchange management shell. Repeat for all servers.

    Add-DatabaseAvailabilityGroupServer -identity DAGName –MailboxServer mailboxservername

    Add-DatabaseAvailabilityGroupServer identity DAG01 –MailboxServer Ex1

  • Click Save and you will see below screen. Interesting to see the time 45 seconds and this estimate was accurate.


  • After 1st server finished, add 2nd node and continue adding all DAG node. This will create the DAG.
  • Now we need to create the database.
  • Click on ServersàDatabases
  • Click on + sign to add new database.
  • Fill the following fields and click on save.

    Mailbox Database = Name of the database

    Server = Browse and select the server on which we will create this DB

    Database file Path = Database path with the databasename.edb

    Log file Path = Log file path

    Check Mount this database if unchecked.


    Or

    Run the below mentioned command from Exchange management shell

    New-Mailboxdatabase -server servername -name DBname -Edbfilepath “DBpath\DBname.edb” -logFolderPath “LogFilesPAth”

  • Database should be created and mounted. But you will see this warning so restart the Information service.

    “Please restart the Microsoft Exchange Information Store service on server EX1 after adding new mailbox databases.”

  • Select the database àclick on and select “Add database copy”


    Or

    Run the below mentioned command from Exchange management shell

    Add-MailboxDatabaseCopy databasename -MailboxServer mailboxservername

  • Now browse and select 2nd database server, click ok then click save.
  • Now seeding will begin to the 2nd or another server.


  • Once seeding finishes restart the information store service on the 2nd or next server.
  • Check the status of the copies by running the command get-mailboxdatabasecopystatus *\*

    You might see the content index is in failed state. This will become healthy after some time of the restart of information store service So go ahead and restart the Information store service.

  • Now DAG status will look like the below screen



Exchange 2019 DAG Blog Ends here

Prabhat Nigam

Team@GoldenFiveConsulting

CTO @ Golden Five | CEO at LAExUG Foundation

Prabhat is 3 times Microsoft MVP Award winner. He is MBA in Information Technology and he is working as a CTO at Golden Five Consulting which is a Microsoft Gold Partner, MSP, T1CSP, and Education partner. He helps in designing, implementing, managing and supporting solutions for private messaging cloud, mergers, a collaboration between different messaging software and other migration & deployment projects for the following technologies Office 365, Azure, AWS, Exchange, SQL, ADFS, MFA, FIM, MIM and Directory services. He has worked for all big IT giants either as an employee or contractor where he has led the Global teams. He has started his career as Technical Consultant in Exchange 5.5 with Microsoft PSS and his exchange love never stopped & continued with 2000/2003/2007/2010/2013/2016/2019/O365. At one point in time, he was the only person to support EDS customers when Microsoft had closed all the supports for 5.5 and now for all old legacy Exchange versions.
He used to blog at MSExchangeGuru.com, manages multiple LinkedIn and Facebook Groups. He also Owns MSExchnageGuru YouTube channel where he uploads all his records technical sessions. Don’t forget to check his PowerShell scripts which are making admins life easier. Prabhat can be reached at PN@GoldenFive.net.

Leave Comment

Your email address will not be published. Required fields are marked *