Results 1 to 3 of 3

Thread: edb file

  1. #1
    Member
    Join Date
    Mar 2016
    Posts
    1
    Points
    0

    Default edb file

    How to get a letter from the damaged database edb? Restore its logs did not work, because got out that there is no error log Fail. Exchange Server gives the following error: "Corrupted or damaged EDB headers"

  2. #2
    Member Spyware Fighter zep516's Avatar
    Join Date
    Dec 2005
    Location
    Pittsburgh, Pa
    Posts
    7,175
    Points
    1308

    Default

    Hello,

    Have you tried a Google search for---> "Corrupted or damaged EDB headers"

    The Topic is not in my skill set and I would be unable to assist you.

    Joe

  3. #3
    Member
    Join Date
    Apr 2016
    Posts
    1
    Points
    0

    Default

    Below guide from one Blogspot, where you can restore all types of Exchange Server data, but if your corruption is complicated, I would suggest you to use more powerful instrument https://www.openfiletool.com/edbopen.html EDB Open File Tool

    In case you have a lack of info about MS Exchange Server database corruption, see and learn following topics...

    http://itknowledgeexchange.techtarge...exchange-2007/
    https://community.spiceworks.com/how...hange-database

    Run Eseutil in /P (repair) mode.
    The easiest way to do this is to have both database files (.EDB and .STM) in the same directory (which they usually are). If they're in different places, you're going to have to point to the files on the command line.
    Eseutil is located in the \exchsrvr\bin directory
    Example:
    eseutil /p c:\exchsrvr\mdbdata\db1.edb /sd:\exchsrvr\mdbdata\db1.stm /te:\temp.edb
    This command line will repair DB1.EDB located on C: along with its matching .STM file located on D: and will put the temporary file on the E: drive.
    If your streaming database file (.STM) is not matched to the database file (.EDB) or it has a problem that is blocking repair, you can add the /i switch to the repair command line.
    The /i option ignores the signature mismatch error in the check phase. The database and streaming file will receive new signatures in the repair phase.
    Repair can take a while--hours. When it finishes, it will leave you with a very detailed log file of what it did called .integ.raw.
    Not quit finished yet, there are two more steps to complete.
    Please see some more links in the conclusion for examples of the command line and a brief intro to the exchange utilities