Decommissioning Exchange 2010 DAG

Exchange 2010 LogoI received a question on if it was possible to decommission a DAG, so that the Exchange 2010 servers would become stand-alone Exchange servers and the databases remain available on one server, freeing up other mailbox servers. I assume the customer has valid reasons for wanting to do so, like downsizing without requirements justifying the DAG. To answer that question: of course that is possible. Now, while many blogs are happy to tell you how to create a DAG there aren’t many on how to dismantle one, so here goes.

For this blog I use a small setup which consists of a single DAG (DAG1) with member servers L14EX1 and L14EX2 hosting two databases, MDB1 and MDB2; both servers host an active copy.

image

In this example we’re going to decommission DAG1, where in the end the L14EX1 will host both databases and L14EX2 is freed up.

Before we decommission the DAG, we’ll reorganize the active databases so when removing database copies we’re removing passive copies. We’ll start by checking if the health status of the DAG:

Get-MailboxDatabaseCopyStatus *

image

We see databases are mounted and copies are in a healthy state. Next, we’ll active the copies on the L14EX1, because we’ll be freeing up the L14EX2:

Move-ActiveMailboxDatabase –Server L14EX2 –ActivateOnServer L14EX1 –Confirm:$false

image

Verify the databases are now properly mounted on the L14EX2:

image

Next, we’ll be removing the passive copies hosted on the L14EX2. Use Get-MailboxDatabaseCopyStatus instead of Get-MailboxDatabase because Remove-MailboxDatabaseCopy needs the database name specified together with the server name hosting the copy, e.g. “SERVER\DATABASE”. Note that after removing the copy, the files are still present on the file system which you need to clean up manually:

Get-MailboxDatabaseCopyStatus –Server L14EX2 | Remove-MailboxDatabaseCopy –Confirm:$false

image

With all passive database copies removed, we can now remove the L14EX2 from the DAG. Note that when removing a non-last member server, the node will also be evicted from the cluster and the quorum will be adjusted when necessary.

Remove-DatabaseAvailabilityGroupServer –Identity DAG1 –MailboxServer L14EX2

image

Next, do the same thing for the remaining node, the L14EX1. Note that this server still hosts (active) database copies which is ok; the cmdlet will detect this is the last member server of the DAG and will also remove the cluster object.

image

After the last member server has been removed from the DAG, we now have an empty DAG object which we can remove:

Remove-DatabaseAvailabilityGroup –Identity DAG1 –Confirm:$false

Et voila, L14EX1 now hosts both databases and the L14EX2 is freed up and you can uninstall Exchange from that server if required.

image

Kindly leave your comments if you have any questions.

13 thoughts on “Decommissioning Exchange 2010 DAG

  1. Pingback: NeWay Technologies – Weekly Newsletter #29 – February 7, 2013NeWay | NeWay

  2. Thank you for simplifying this task. Your example and step-by-step explanation made perfect sense.:)

  3. Pingback: Remove a DAG with Active Databases and other Exchange Tricks | Adventures of an Oregon K12 IT Director

  4. Maybe you should just add a note concerning Public Folders that need to be replicated before decommissioning the old server. I know this article is focused on DAG, but forgetting about PF before killing a server can be a problem. Besides this, great article.

  5. Once the servers are stand alone, can I then proceed to uninstall Exchange? I’ve been unable to uninstall the mailbox role because the mailboxes still exist. I used the remove-mailbox PS command and effectively deleted over 780 active directory accounts – that was a HUGE screw-up. We are no longer using Exchange and the servers are ear-marked for another project. I need to decommission Exchange properly so in case we ever want to go back to Exchange, it will be possible to re-install.
    Any extra advice on that set up?

  6. Hi,

    Is it ok to follow this for one server recovery? Actually, We have 2 Node DAG with multi role. No Edge server. Now, we are doing some disaster recovery testing. We did restore one of the DAG member using setup:Recoverserver installation and did clean up second server and removed DAG as well. After that we restored the database from backup to server original location. To mount database, we changed restore database “MasterTyper” from “DatabaseavailabilityGroup” to our server restored server FQDN name. Everything is working fine except our current outlook client is is not able to connect with this. I can configure new outlook profile and its working fine but we need this recovery should work with our current setup. Please note: For this testing, we restored the Domain Controller as well. Please suggest, you can help us to point out cause of this this issue.

    • 1) Why recover from backup – reseed was not an option? (recovered copies are often too outdated, causing divergence and reseeding anyway);
      2) What doesn’t work – is the certificate reinstalled?
      3) At what moment – and why – did you restore the DC?

      • Here is brief steps we followed for testing environment.
        – Restored one of DC from Backup (2 Week Old) and transferred all roles to make it workable
        – Restored one of DAG member which had active copies from Backup(latest backup)
        – Clean up like removed database copy,removed other member server from DAG, removed DAG completely.
        – Point the casarray name to recovered server IP
        – Restored the database to original location (Recovered server) thorough Symantec backup Exec.
        – Changed “MasterType” and “MasterserverorAvailabliltyGroup” to “server” and “FQDN of Recovered server”
        Then we did following testing –
        -Outlook new profile creation (Successful)
        -OWA access (Successful)
        -Autodiscovery (Successful)
        Now, we thought to connect one of production environment client to this testing environment but it failed to connect. I hope this will enlighten you more about my query.

        Please suggest.

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s