Public EDB reconstruction from logs after crash

Please note that this is the fr-fr  forum. We kindly recommend posting your question in Frech so that more community members can assist you. Alternatively, you may consider posting in the English forum if you prefer to use your native language. We sincerely appreciate your understanding 
Hi @Laurent Lehmann

Thanks for reaching out to the Microsoft Q&A forum.  

Based on my research, after running a recovery using eseutil /p, the restored database is treated as a new database. Because the repair process modifies the database header, the database signature also changes. As a result, the repaired database no longer matches the sequence or signature of the transaction logs from 2019 through the present. This mismatch causes the log replay process to stop at the 2019 logs.

Since the signatures no longer align, native tools such as eseutil cannot continue the log replay, as the log files are no longer compatible with the repaired database. 

To work around this situation, you may consider recovering the public folder data from another available data source, such as: 

• Local OST file: If any user enabled Download Public Folder Favorites in the Classic Outlook desktop app, their device may contain locally cached public folder content. While this data may not be complete, it could allow you to recover at least part of the public folder structure. 
• Third‑party tools: Some administrators have reported success with third‑party utilities that can read repaired databases or work around log mismatches.  Example reference:  Replay/Truncate log files exchange 2010 without having ever made a backup - Server Fault 

Since different environments may require different recovery approaches, you may review available third‑party options and choose the solution that best fits your scenario. 

This information is provided as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link. 

I hope this provides additional insight. If you have any updates, please feel free to share them. 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.