Why does an Exchange 2013 mailbase go offline after indexing?

Question

Microsoft Exchange

After replacing the disk in the raid, during rebuilding, a failure occurred. As a result, the virtual machine files, vhdx. On the Exchange server, after the startup was restored, it was found that the database containing mailboxes (actually, mailbox.edb) is not connected. The VM backup file was also damaged (no, it was not the same partition of the same disk, but nevertheless), but it was possible to extract a more or less complete copy of the database from it, as well as log files. A soft recovery was performed via eseutil, the database was connected back to the Exchange server. A "Content index status: FailedAndSuspended" error was also encountered, which is resolved by deleting the indexes and restarting the search service. After that, the state of the index changes to Crawling, the database starts to be indexed, the mail goes, everything works, but after indexing, the database gets the Failed status and will be unmounted. What could be the reasons and how to eliminate them?

Answer 1

I advise you to score on the index, create a new database, move all the boxes to it and then unmount the old database. Well, take care of application-level backups.