Among the many tasks an Exchange administrator has to perform, restoring, moving or migrating Exchange mailboxes on the server is a major one. Though most of it involves a typical set of scripts that need to be run with minor tweaks, sometimes, the process gets interrupted or worse, fails due to unforeseen reasons.
In this article, we're discussing one such instance in which, mailbox move / restore operation on the Exchange server fails with an error code 1056749110. If you've worked with Exchange long enough, it's unlikely you haven't faced this error at least once. Let's dissect this error and find out all that we can about it.
Usual steps for recovering Individual Mailbox items
There are several techniques to recover individual mailbox items for an Exchange server mailbox. Typically, using Windows Server Backup, this process includes the following stages:
Usually, all these stages progress without any flaws if all specified parameters are correct. However, for some mailboxes, restoring / moving the contents could fail with error code 1056749110.
What is this error all about?
If the mailbox move / restore operation fails with error 1056749110, you'll face the following error message:
Restore-Mailbox: Error was found for RSG, Test because: Error occurred in the step: Moving messages. This mailbox exceeded the maximum number of corrupted items specified for this move mailbox operation, error code: -1056749110
This error occurs because of the presence of corrupt items in the mailbox. While the restore / move operation is underway, if corrupt items are found in the mailbox, the execution retries to complete the operation several items. However, it gives up after a certain limits of retrial attempts and throws this error.
How to fix the error?
You can try to fix Exchange error 1056749110 through two methods:
Let's skin through these one by one.
To solve this error manually, we'll try to restore a sample mailbox (that has corrupted items) from RSG to a production mailbox. Here is the command to do this:
Restore-Mailbox -RSGMailbox "RSG, Test" -RSGDatabase MySmpl-Exch\RSG_DB\db11 -id "Recovery, Mailbox" -TargetFolder "Recovered Mails of RSG mailbox"
Here is a description of the various parameters in this command:
Since we have purposely picked a mailbox that has corrupted items, this command is expected to fail with the error 1056749110. In order to stop this command from failing, add the BadItemLimit switch to the command as follows:
Restore-Mailbox -RSGMailbox "RSG, Test" -RSGDatabase MySmpl-Exch \RSG_DB\db11 -id "Recovery, Mailbox" -TargetFolder "Recovered Mails of RSG mailbox" –BadItemLimit 1000
The BadItemLimit switch tells the command to skip bad or corrupted items in the mailbox. The number following the switch is the total number of items to be skipped. The valid input range for this switch is 0 to 2,147,483,647 (where giving input as 0 is the same as not specifying the parameter at all).
Using third-party automated tool
Though the above mentioned method works for most cases, it might not achieve its purpose in rare cases. At such times, you can use competent third-party EDB repair software Stellar Repair for Exchange. This product is adept in repairing corrupt or damaged EDB (Exchange Database) files to restore inaccessible mailbox items. Using this tool will give you two major advantages over the manual method:
So, there you go! The next time your Exchange mailbox move/restore operation fails due to corruption, you know exactly what to do and how. And don't forget to make the process easy by using automated software.
This article explains to get back all their old mail and restore the original mail from crashed Exchange server. Explore all technical know-how or the right tools in hand to have a quick recovery with minimal downtime, for the Exchange Admins.
Experts recommend to use Eseutil/mh command to identify Exchange database state. If your database in ‘Dirty Shutdown State’ then use eseutil/mh commands to change the database state to ‘Clean Shutdown’.
Run ESEUTIL /P commands to complete Exchange database hard repair process using . ESEUTIL /P – repair corrupt or damaged exchange database EDB files smoothly.
how you can repair a PST file after a changes with MDBVU32. This free method also supports Windows 10 and Outlook 2016.
Useful tips to fix file File Level Exchange Server Database Error 1018, 1019 and 1022. It is applicable for all Exchange Server versions 2016 / 2013.