Forum Discussion
Deleted
Jun 12, 2023Exchange 2013 mailbox migration
Unable to migrate mailbox from on-prem to exchange online.
We got the following error in the log.
(DBname)’ is unhealthy and shouldn’t be accessed.
- DeletedJun 12, 2023
HiDeleted
This error can be generated if an index in the on-premises environment is corrupted. try the below.
Rebuild the content index catalog on the on-premises Exchange server. For more information about how to do this, see Reseed the search catalog.
After the index catalog is rebuilt, wait a few minutes until the fast engine starts indexing again.
Determine whether indexing is completed. To do this, run the Get-MailboxDatabaseCopyStatus cmdlet.
If indexing is completed, the value in the output should show as Healthy.
After indexing is completed, perform the mailbox move request.
If I have answered your question, please mark your post as Solved
If you like my response, please give it a Like
Appreciate your Kudos! Proud to contribute! 🙂
- Deleted
HiDeleted
This error can be generated if an index in the on-premises environment is corrupted. try the below.
Rebuild the content index catalog on the on-premises Exchange server. For more information about how to do this, see Reseed the search catalog.
After the index catalog is rebuilt, wait a few minutes until the fast engine starts indexing again.
Determine whether indexing is completed. To do this, run the Get-MailboxDatabaseCopyStatus cmdlet.
If indexing is completed, the value in the output should show as Healthy.
After indexing is completed, perform the mailbox move request.
If I have answered your question, please mark your post as Solved
If you like my response, please give it a Like
Appreciate your Kudos! Proud to contribute! 🙂
- Deleted
hiDeleted
thanks it was indexing issue