Technique to Recover Exchange Server 2010/13/16 using PowerShell Commands

Summary: The common reason for Exchange server failure is the corruption of database files. In this write-up, we will be discussing the solution to recover Exchange Server 2010/13/16 using PowerShell Commands.

Many times, Exchange Administrators face the occurrence of corruption. The moment when they come across such situation, they search various ways for repairing and recovering Exchange database. In fact, there are some common problems where Exchange administrators come across the logical errors, often known as mailbox damage.

Users can execute commands either in PowerShell or in Exchange Management Shell. The actual thing which is recovered in Exchange recovery is Exchange Database file (EDB) in which user mailboxes are stored and each mailbox relates to one user, group etc.

Way to Recover Exchange Server 2010/13/16 using PowerShell commands

Users can use the New-MailboxRepairRequest cmdlet, as it can be run against the whole database or just one mailbox. If the user runs the command against a single mailbox, then mailbox will have interrupted service and not all other users in that database are affected. Some areas can be checked while performing such action is mentioned:
  • Search corruption folder
    This option verifies for all folders that are named in ptagSearchBacklinks, ptagRecursiveSearchFIDs, and ptagSearchFIDs. If the folder does not exist for longer time, then it eliminates it from the list.
  • Counting aggregate on folders
    It tallies all the messages that are present in a folder and keeps on total counts and sizes. Once the iteration is completed, it checks the computed counts that are against the preserved counts on the folder table record. If there is any difference, it will update the preserved counts from those it has calculated.
  • Provisioned Folders
    It checks it with unprovisioned parent folders and vice versa.
  • Folder view
    Repeats all views for a folder and then, reconstructs a temporary copy of it. However, if there is a difference between the two then it will delete all its view and it will be rebuilt from scratch if it is requested next time.

It also includes a switch of detectonly. This switch is useful in a case where it is important to simply report on the issues without making changes. This switch will not affect the service of user.

It is safe to use in a situation where user does not receive any notification of service interruption. Although, that point might lead to repair any detected damage by using this cmdlet and will affect the user.

Rapid Solution: Users can go for Exchange Database Recovery Software provided by SysTools which easily recovers and repair the offline/dismounted Exchange database file from corruption automatically without using any PowerShell command. This Exchange Migration Tool provides scan mode option (Quick and Advance scan) which recover corrupted Exchange mailboxes and EDB file without any loss of data in a hassle freeway.

Any users can use this tool, as it provides graphical interface which makes the work easier and save their time. After recovery users can export the recovered and healthy EDB mailboxes to Live Exchange Server, Office 365 and various file formats. For backup the data, you can export EDB to PST, EML, HTML, MBOX, MBOX, MSG file.

Download Now Free Purchase Now 100% Secure

Use PowerShell Command to Recover Exchange Server 2010/13/16

Use the New-MailboxRepairRequest cmdlet given below to repair the Exchange database mailbox:


The value of ‘MailboxID’ can be SMTP address, DN, UPN, GUID, alias, LegacyExchangeDN or in the domain format, it will be a ‘domain\user’. Some more verification of user’s mailbox by reviewing the four areas and completing the repair at once would interrupt the user’s service. Then, the user needs to run the command that is mentioned below:


A database check for only search folder corruption would be similar to: new-mailboxrepairrequest

There is no direct output into Powershell console. User can open the application event log of Exchange Server. Begin it by checking for “MSExchangel S Mailbox Store” events having the event ID 10047 and 10048. User can make the things more clear and challenging if user have run New-MailboxRepairRequest cmdlet more than one then, the event log will only view the mailbox by GUID.

To help in finding the right one, user can run



In the above discussion, Exchange database recovery is described. A technique to recover Exchange Server 2010/13/16 using PowerShell commands is discussed. According to experts, it is the main challenging task for the users to recover their Exchange Server database.