This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 48%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hello,
I have unfortunately made a big mess. After our Exchange server could no longer be started and I noticed that the hard disk was full, I deleted about 34,000 transaction logs (E00XXXX files), assuming that they were not needed. Unfortunately, I did not realize until too late that these were relevant system files.
Because the state of the DB was set to Dirty Shutdown, I did a eseutil /p DB.edb afterwards. Currently the state is set to Clean Shutdown, but the DB cannot be started anymore because of the missing logs.
Unfortunately, the last full backup of the affected server is almost 70 days old. Do I have a chance to get the Exchange Server up and running again with halfway current data?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Hi @ma_schulte
I am writing here to confirm with you how thing going now?
Please let us know if you would like further assistance.
Yea, this is tough.
If you move the checkpoint file to another location (*.chk), and try to mount, is it successful?
If that doesnt work, follow the steps here:
https://techcommunity.microsoft.com/t5/exchange-team-blog/new-support-policy-for-repaired-exchange-databases/ba-p/603723
If you can get to mount, you need to create a new database and move the mailboxes to it to be supported.
Uncorrectable corruption can linger in a repaired database and cause store crashes and server instability, we have changed our support policy to require an evacuation of any Exchange database that persistently has a repair count or old repair count equal to or greater than 1. Moving mailboxes (and public folders) to new databases will ensure that the underlying database structure is good, free from any corruption that might not be corrected by the database repair process, and it helps prevent store crashes and server instability
If you move the checkpoint file to another location (*.chk), and try to mount, is it successful?
That solved the problem, thank you very much!
Unfortunately too early rejoiced... some mailboxes work again as usual, with some a login is not possible.
Via OWA I get the following error message: SDServerErr;Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException.
Thats expected. When you run a repair, it pretty much ensures that some stuff will be busted and data will be missing.
Repairs are a last resort and destructive.
See my previous link:
If you can get to mount, you need to create a new database and move the mailboxes to it to be supported.
Uncorrectable corruption can linger in a repaired database and cause store crashes and server instability, we have changed our support policy to require an evacuation of any Exchange database that persistently has a repair count or old repair count equal to or greater than 1. Moving mailboxes (and public folders) to new databases will ensure that the underlying database structure is good, free from any corruption that might not be corrected by the database repair process, and it helps prevent store crashes and server instability
Thank you, I have proceeded exactly as described. Unfortunately, access to the two affected mailboxes is still not possible. Also moving the affected mailboxes to a new database does not work. The value StatusDetail when queried via Get-MoveRequestStatistics is set to MDBOffline (stuck at 20%). Is there any hope for the affected mailboxes?
There may not be unfortunately. The repair process can be rough.
Are the two affected users using Outlook in cache mode? If so, they could go offline, copy their mailbox to a pst and start with a new mailbox.
Otherwise, you may not be able to recover those two mailboxes.
Yes, thats what I already did for those two users. Unfortunately, only the data from the last 6 months is cached. I still have a healthy backup of the entire server from 2 months ago. Is there a possibility to export the mailbox from the old edb?
You could try a recovery database and make a copy if the DB for it.
But if wont let you move the mailbox, it may not allow exporting either.