Issues with Exchange to O365 restore after cryptolocker

[christiankelly]

We have a client that got cryptolockered backups and all. Thankfully we had CloudConnect in play and are slowly getting everything rebuilt and restored.

An Exchange 2013 server was in place, and to get communications flowing, we setup Office365 and empty mailboxes with the plan to restore the older mail through Veeam.

We have been attempting to restore the mailboxes but are running into a lot of issues. After a mailbox restores, it will say something like 40,000 emails restored and 20,000 errors. And when looking inside the mailbox in some cases, the items which errored are restored, but in others not. In a lot of cases, there are five copies of each email, but not in all. It seems random at this point. We have 150 mailboxes to restore and only restored about eight and all have issues so far.

The errors in the GUI are "Error; Failed to create items. SOAP header Action was not understood," and in the logs, there is a lot about SOAP errors and "Failed to create items. The account does not have permission to impersonate the requested user." The account used to restore has both full access for each mailbox as well as "delegated admin."

I have opened a support case, but so far, I'm getting "We don't know what Microsoft/EWS is doing so not much we can do."

Has anyone seen this or had issues restoring to 365?

Thanks,

[christiankelly]

Veeam support is recommending we scrap the direct restore, export to PST and upload manually. That’s disappointing.

[nielsengelen]

Chris, while restore to other location may work, it may not always work for every item. Could you share us the support case ID so we can have a look at the case as for now we can’t assist much more on here.

[christiankelly]

Yes that’s why we’re trying so hard to make this work as the PST import option doesn’t bring back all items correctly.
Case 04073556