Using Mailbox Repair Request Command for Exchange 2010

How to Use Mailbox Repair Request Exchange 2010? Get the Solution

Summary: Do you want to know how to use mailbox repair request Exchange 2010 to detect & fix the Exchange database mailbox corruption issue? If yes, then read the article and find the solution to repair the corrupt Exchange EDB mailboxes.

The concept and dependability on IsInteg Tool was dropped with the introduction of Exchange Server 2010. However, in versions older than 2010, Exchange Server depended on “New-MailboxRepairRequest” command line for detecting and repairing Exchange mailbox corruption issues. The tool came as a complementary utility with the ESEUtil; which was meant for the maintenance, verification, and repair of the ESE database (Exchange databases included). While IsInteg checked and helped in repairing damaged integrity of the Exchange database.

NOTE: The most important advancement made in Exchange 2010 was that unlike its earlier versions, repairing or checking database didn’t require taking it in offline mode anymore.Exchange 2010 comes with ESEUtil but as part of its Mailbox Server Role. It runs in the background all the time and not for maintenance but for inspection and recovery of database instead.

TIP: Even IsInteg is a part of Exchange 2010 Mailbox Server Role but you are advised not to use it as it hasn’t been updated to interpret the structure of Exchange 2010 database. Thus, using it on 2010 database might result in its inconsistency.

Exchange 2010 SP1 – New-MailboxRepairRequest

IMPORTANT: These procedures cannot be performed in EMC (Exchange Management Console). You ought to have the Exchange Management Shell.

1. New-MailboxRepairRequest
2. New-PublicFolderDatabaseRepairRequest

However, it is important to be aware of the fact that, like other Management Shell cmdlets, these two are subject to RBAC (Role-Based Access Control) evaluating limitations.

Using Mailbox Repair Request Command for Exchange 2010

When using the repair request for your Exchange database mailbox the command line to be used has been provided below with the respective values to be used.

TIP: The Parameter ‘DomainController’ is to specify Fully Qualified Domain Name (FQDN) of Domain Controller, which is responsible for writing the configuration changes to Active Directory.

To Detect Corruption In Mailbox

If you want to directly repair your mailbox and detect for issues in it, remove “DetectOnly” parameter from the command and run it.

NOTE: In case you are unable to see any mailbox result in the output result, then check the EVENTLOG application to find out the cause of blank mailbox result in repair status.

Services of Using Mailbox Repair Request Command for Exchange 2010:

The mailbox repair command in Exchange 2010 is the source to detect and repair the listed types of corruption in Exchange mailbox:
i.             Search Folder Corruption: Using SearchFolder value of CorruptionType parameter – Checks all folders for their existence and the ones that don’t, are deleted from the list.

ii.    Aggregate count for directories not reflecting the correct value: Using the value ‘AggregateCounts’ of parameter ‘CorruptionType’ – Check folder messages, and updates incorrect message count and size.

iii.   Folder views on directories not reverting correct set of content: Using the value ‘FolderView’ of the parameter – ‘CorruptionType’ – Checks contents of folders and if found incorrect, they are deleted from the view.

iv.   Provided directories incorrectly point to parent directories that have not been provisioned: Using the value ‘ProvisionedFolder’ of ‘CorruptionType’ parameter – Looks up the problem and fixes it accordingly.

TIP: To avoid performance related issues, kindly note that, Microsoft Exchange enforces limitations on the number of concurrent repair requests that are permitted to be submitted by each server. For the database level of repair only one mailbox repair request can remain active, while when executing a mailbox-level of repair for a server each 100 requests can stay active.

NOTE: Once the repair request has been commenced, you can’t be interrupted / stopped unless the database is dismounted.

Mailbox Repair Request Exchange 2010 And Its Parameters – Points To Note

1. The New-MailboxRepairRequest cmdlet is helpful in detecting and repairing mailbox corruptions.
2. The command can be run against either a preferred mailbox or even against mailbox database.
3. However, running the command makes mailbox access become disrupted.
4. Note that only the mailbox against which the command is running will be disrupted from access and others will remain operational in the meantime (in case of mailbox database repair).

Output Displayed On Executing Mailbox Repair Request Exchange 2010 Command

When using the Exchange 2010 New-MailboxRepairRequest, the following types of output, will be displayed on screen:

• RepairTaskID – The value is used to specify a unique identifier for repair task.
• Mailbox – The mailbox in the process of being repaired is specified by this value. NOTE: On the specifying database level repair, the value will be left blank.
• Database – Denotes the database containing the mailbox that is being repaired.
• Server – Mailbox server is specified by this value that is hosting the currently active copy of the database which is containing the mailbox under repair.

Note: There are times when due to corruption the Exchange database goes into offline or dismounted state. Then the solution provide here doesn't repair the Exchange .edb file and mailboxes. In that case, users can use the SysTools Exchange Recovery Tool which supports this Exchange database file (Public & Private) and used by many technical and non-technical users to repair and recover Exchange mailbox from corruption in a simplified manner without using any cmdlet. After recovery, users can export the recovered EDB mailboxes to the Live Exchange Server 2016/2013/2010/2007/2003 mailboxes, Office 365, and multiple file formats.

Bottom Line:

When working with cmdlets, be very careful that the values and parameters used in the command line are spelled correctly. Even the smallest of errors incorrectly writing the command can lead to the failure of the mailbox repair process. Hence, this might mislead you in terms with the correct mailbox status whether corrupt/healthy. If you still couldn't repair the mailbox then you should go for any Exchange Recovery Tool.