I've restored an Exchange 2013 database using SC DPM to a recovery database. This worked and it is mounted. Now I'm trying to use the MailboxRestoreRequest to restore a single mailbox from there to the live DB. It's gets queued, but after several days, nothing is happening. I've tried canceling the request and restarting the server and running it again, but it hasn't helped.

Hello

get restore log:

Get-MailboxRestoreRequest -Ident mailbox |MailboxRestoreRequestStatistics -IncludeReport |fl

Hi Mike,

From your description, I recommend you use the following cmdlet to check the detailed restore information:

Get-MailboxRestoreRequest | Get-MailboxRestoreRequestStatistics | fl percentcomplete,itemstransferred,*count*

Hope this can be helpful to you.

Best regards,

Thanks, but it looks like nothing is happening.

PercentComplete            : 0
ItemsTransferred           : 0
BadItemsEncountered        : 0
LargeItemsEncountered      : 0
EstimatedTransferItemCount : 0

Apparently, the following switch was supposed to be used to restore to a production mailbox (-SkipMerging StorageProviderForSource ) but this seems to have been remove in CU6. So it's still stuck in queued.

Hi,

It seems that the mailbox restore request is queued at 0%. Please check your database replication and verify if it is in a failed and suspended state. If yes, you need to start it and check the result.

Hope this can be helpful.

Best regards,

I tried adding a new mailbox to restore to, and at least now it's getting beyond "queued". It goes to "In Progress", then failing with the following error.

The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.

Database: RDB-CONTROL

Error: MapiExceptionRecoveryMDBMismatch: Unable to open message store. (hr=0x80004005, ec=1165)

Hello

get-mailboxstatistics -database RDB-CONTROL add user list?

I ran the command and yes I can see the mailbox I'm trying to restore in is in the database.

Hello

and after Exchange Mailbox Replication service restarted?

Hi,

The above error occurs because the MailboxReplicationService currently caches Mailbox Database information past the lifetime of some databases.  You can restart the service to clear the cache and check the result.

Hope this can be helpful to you.

Best regards,

Hi,

Any update?

Best regards,

I'll be getting back to this soon. Got sidestepped by a different issue.