Toll Free: +1 888 900 4529 |   Toll Free: +44 800 088 5522

How To Recover Exchange Server 2013 After Exchange Domain Controller Failure

Angelbrown Leka | September 4th, 2014 | exchange 2013

Exchange Server, the foremost Client-Server application is used by various organizational setups all around the world. The situation when Exchange Server crashes often compel users to think how to recover Exchange Server 2013 as Exchange 2013 is highly picked for organizational data management. With some pre-requisites, Exchange Disaster recovery method that is associated to Domain Controller will work towards Exchange database revival.

Note: Before getting started with Exchange Domain Controller, one should know the limitations or conditions:

  • Exchange account must have membership of Domain Admins Group & Enterprise Admins Group
  • Exchange Organization Management Group membership is also required for the particular Exchange user account

Getting Started – Disaster Recovery Exchange 2013

The reach of Exchange database for proper disaster recovery is the basic need. The domain controller is the best equipment to perform Exchange database recovery. If the user is looking for Exchange database recovery when there is single Domain Controller playing the role of Exchange Server, then it is not possible. There should be a member Exchange Server, it is a good practice to offer better results. All recent editions of MS Exchange will work with this concept, even the steps of the procedure will not remain same.

Exchange 2013 Disaster Recovery Step by Step

To set the platform for Exchange database disaster recovery, the requirements will be:

  • Domain Controller Exchange 2013 should be in reach and in functional mode
  • The OS name and the Server name should be same

ad-os

Server details under Active Directory rights

  • Find the host name of Server that is crashed into DNS Server that is integrated to an Active Directory, once you get the desired IP then put it right place.
  • Drive letters should match else, user may see failed process

drive-letter-1

To do this help of ADSIEDIT navigate the above mention location

Navigate to the properties of “Mailbox Database 1679725872” and not down the below mention values for the drive letters which has the locations of log and database file.

  • msExchEDBFile location
  • msExchESEParamLogFile location
  • msExchESEParamSystem location

Note: It is required to get complete knowledge of ADSIEDIT before moving on to use the tool.

Brief Information about ADSIEDIT
It’s an editor for Active Directory and manages the associated objects/attributes. Moreover, it is abbreviated as Active Directory Service Interfaces Editor. Under the forest of selected directory adsiedit.msc permits to get the preview of Exchange objects with associated attributes. For having a view of attributes, editing of objects, and making queries for particular objects, the ADSI EDIT will be used.

When you are done with Exchange 2013 Disaster Recovery Setup by setting the basic pre-requisites, the steps to recover Exchange Server 2013 using Domain controller concept will be:

  • Add Server to domain for which the path will be:

Active Directory Users and Computers >> Crashed Server (make right click on it) –Reset Account

active-directory-setting-2

After rest the Account then you will be able to add same server of the domain

  • Add machine to domain,verify the information of Exchange server is available on the domain. You can verify it through the any domain controller after login then open ADSIEDIT

ADSIEDIT –> Start -> Administrative tools should be your selection -> ADSIEDIT (right click) -> Connect to -> selection of Naming Context -> follow Configuration under drop-down list

  • Check out Server object for DN which is crashed and needs recovery

dn-server-object-3

DN of the Exchange Server.

  • Finding the location of DN in GUI

exchange-server-dn-4

  • Roles, features, attributes, and associated objects under Active Directory should check properly.

Before opting the PowerShell Commands, it is required to install “Import Module Server Manager”.

Run this following command on PowerShell.

import-module-server-manager-5

Install the application properly, then restart the Server after getting updates for roles and features also. To pick up the desired application from the Microsoft Site, you can follow this link. Click Here to move ahead.

To get other updates to perform the actions properly follow the article KB974405

Now you need to set log file path and database file path, when you are performing the process both of these paths will be varied.

Location of Microsoft Exchange Server in the System

exchange-server-2013-path-6

Restore data file path

exchange-server-2013-file-location-7

Note: Log file and database file path is different in particular scenario

Now you need to download Exchange Server 2013 on your computer. To get the download that you will have to save at local drive, click here.

In Windows PowerShell, type the command given as:

powersheel-recover-server-8

Run this command: Recover Server Switch

powersheel-recover-server-status-9This window show the Configuring Prerequisites

powersheel-recover-server-configuring-prerequisites10

The Exchange disaster recovery for Exchange 2013 is now done and the other step will be placing the recovered database at right place. Mounting the store after restoring database should be your responsibility once you are done with Exchange database recovery with Domain controller.

Now open Exchange Admin Center >> click on “Server” from the left pane then >> hit on “Database” tab then select the “mount database” tab

exchange-admin-center-11

Once mount operation is done. All emails will be restored to desired Exchange mailboxes and users will be able to perform send/receive operation.

outlook-web-app-12

Necessary Points To Remember

  • Healthy backup of Exchange databases is required.
  • Server databases will be recoverable, if it is all about Member Server.
  • To recover the database easily and safely, Active Directory must have healthy nature.

What To Do When Domain Controller Fails To Recover Exchange Database?

If it happens again, then you will have to think how to recover Exchange Server 2013. The best and effective way to cut down all the limitations of Domain Controller Exchange Disaster Recovery is using Exchange Recovery tool. This tool works stand-alone and works for all annoying conditions where Exchange database recovery is required.

The following two tabs change content below.

Angelbrown Leka

Angelbrown Leka is a software developer by profession. She loves to write technical blogs over distinct topics pertaining to the issues of Exchange server and Outlook environment. She has earned certification in MCTS and her areas of specialization are MS Exchange server and Outlook platforms.