Recover Exchange Server 2013 after deleting transaction logs

ma_schulte 1 Reputation point
2022-03-01T10:08:25.99+00:00

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?

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,384 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Andy David - MVP 142.7K Reputation points MVP
    2022-03-01T11:57:00.513+00:00

    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

    1 person found this answer helpful.