Doubtlessly the Microsoft Exchange Server is the most popular mail and calendaring server used by many IT organizations & other industry verticals around the globe. There are large number of mailboxes data stored in various Exchange mailboxes in the EDB (Exchange Database). It is natural that we have to prevent the Exchange database from corruption. There are various reasons because of which corruption can occur in the .edb file and one such reason is Exchange database reached maximum size. Users can resolve the corruption issue by using New-MailboxRepairRequest to repair Exchange 2013 database described in this write-up.
This New MailboxRepairRequest PowerShell command is the successor of the Isinteg utility. It easily detects corruption in Exchange database mailboxes and database. Users can execute or run this cmdlet against the mailbox or the entire database.
Users cannot access the Exchange mailbox when they run the command. The New-MailboxRepairRequest cmdlet only applies to Exchange Server 2019, 2016, 2013, 2010. You can only implement one request for database-level repair or for the mailbox-level repair you can apply 100 request.
There is no need to dismounting the Exchange database to repair it from corruption because the PowerShell command works in online mode. When the user run the command to repair Exchange 2013 database, then it can’t be stopped until the database becomes dismounted.
Note: When you are new to the Microsoft Exchange Server environment then it becomes difficult for users to understand the cmdlet to repair corrupt Exchange mailbox and EDB file because it requires in-depth knowledge, technical skills, and hands-on experience to understand and handle the problem. So, to avoid all these complexity and technicality you can use the advanced solution described in the below solution which saves users time and effort too.
Rapid Solution: User can opt for the advanced software i.e. Exchange EDB Repair Tool used by various IT professionals, Exchange & Novice users to repair minor or major corrupted offline/dismounted Exchange database and mailboxes without using any cmdlet. Technical & Non-technical users can use the Exchange Granular Restore tool as it provides graphical interface that makes the users work easier & saves time and effort. It Offers Quick & Advance scan mode which repair corrupt Exchange mailbox and EDB file in a hassle-freeway. After recovery, users can export the recovered Exchange database mailboxes directly to Live Exchange Server 2016/2013/2010/2007/2003 mailboxes, office 365 and multiple file formats.
Users can use this cmdlet to repair 4 types of corruption that is given below:
Use the following cmdlet given below to repair the Exchange mailboxes and database:
1. Detect & Repair folder view for John Exchange Mailbox
New-MailboxRepairRequest -Mailbox email@example.com -CorruptionType FolderView
2. The command given below will only detect & corruption problem on Search & Provisioned folder for the Cat mailbox
New-MailboxRepairRequest -Mailbox Cat -CorruptionType ProvisionedFolder, SearchFolder -DetectOnly
3. Use the following cmdlet to repair & detect the aggregate count for all the Exchange mailbox on Mike database
New-MailboxRepairRequest -Database Mike -CorruptionType AggregateCounts
4. The command given below detect and repair all corruption type for Lord Mailbox & archive
New-MailboxRepairRequest -Mailbox Lord -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,FolderView -Archive
5. To detect & correct all existing corruption problem, create a variable to identify Lauren Exchange database mailbox. Later on, this variable is used to specify values for StoreMailbox & EDB parameters to generate the request.
$Mailbox =Get-MailboxStatistics Lauren
As we all know that Exchange Server is prone to corruption. So, it is necessary to keep the database safe & secure from corruption to prevent data loss. Now users have complete information on how to use New-MailboxRepairRequest to Repair Exchange 2013 database and mailboxes from corruption. If the users receive event ID – 10049 which means that the repair request cmdlet is failed. In that case, it is suggested to use the automated wizard described here which easily recover minor as well as major corruption from offline/dismounted Exchange database file in a hassle-freeway without any hindrance. After recovery, users can export the recovered Exchange mailboxes directly to Exchange Server, O365 and various file formats.