It looks like you're new here. If you want to get involved, click one of these buttons!
The section highlights the changes in Exchange 2010 database structure at logical level in comparison to its previous versions. Also, it explains how to repair Exchange 2013 mailbox without ISInteg utility when there is inconsistency in mailbox at logical level.
Those who have been administrating MS Exchange from a long time must be aware of the ISInteg utility that fixes issues with logical structure of the database. However, ISInteg no longer exist from Exchange 2010 edition and its job is performed by set of some online cmdlets.
Earlier to Exchange 2010, the database schema have tables organized at database level. Therefore, corruption in a table affects the mailboxes in the database. The current schema is more centered to the mailbox tables due to which logical corruption at database level is very less, means low chances of entire DB being affected due to table corruption. However, this has increased the possibility of damage at mailbox-level.
Since most of the data is stored in tables of the mailbox, simply moving it to another mailbox is a solution to various problems. In that case, the bad items are left at the source server and the healthy data is migrated to the target server.
Exchange 2013 Mailbox Repair with Online Cmdlets
For Exchange 2013 administrators, repair mailbox data from EDB file has been an easy job and the credit goes to the New-MailboxRepairRequest PowerShell command. The best part is a mailbox can be repaired without affecting accessibility of other mailboxes in the database. Also, access to the mailbox will be restricted till the time repair is processed.
In order to avoid performance issues, Microsoft has added the limit to number of mailboxes that can be submitted per server. At a time, the repair request can be accepted for one database only with 100 mailbox repair requests activated. There are four types of mailbox corruptions that are detected and fixed by the PowerShell command.
Search Folder: This will check out for the links to the folders that no longer exists and will repair them.
Aggregate Counts: This will check for the aggregate count that is not showing the correct values and fix them.
Folder View: This will check for incorrect content in the folder view and fix it.
Provisioned Folder: This checks out if the provisioned and Un-provisioned folders are properly linked.
Nevertheless, when there is need to detect the type of corruption in the mailbox, the –DetectOnly parameter is used along with the standard cmdlet. Also, there is benefit of pipelining PowerShell operations too. For example: The results of Get-Mailbox cmdlet can be piped into the New-MailboxRepairRequest.
If the online cmdlets do not work as a solution to how to repair Exchange 2013 mailbox due to improper permissions or resource availability, then an alternate can be adopted to repair mailbox data from EDB file to Outlook PST which saves data from loss.
Author Bio: The Company is reputed for their performance-oriented tools in data recovery domain. With Exchange Server Database Recovery tool, it has offered a simplified platform to users to restore mailboxes from corrupt EDB files.