Hard drive failure edb file not recovered missing log files

Tags:
EDB
Hard drives
Microsoft Exchange
Windows Server 2012
Hi I have an Exchange 2013 running on server 2012. They had a hard drive failure on their exchange drive and no working backup. The hard drive was recovered luckily with 98% recovered however not the edb database file. No problem I have the log files ill just replay the log files. however there are a few missing and it stops at the first one which is only 6 month into a 4 years of emails. Is there any way to skip or create a dummy logs? I understand that the emails in that log has gone but any way to skip, cant find anything online Thanks in advance Dave

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Subhendu Sen
    This is not possible to say something fruitful from this side. Why was the hard drive fail, that you did not mention here. How the HDD recovered and is it a reliable/authentic that is also an issue. Why there is no backup, while assuming this is your company. Is there no rule set for this?
    124,170 pointsBadges:
    report
  • Gulab Prasad
    If you have database file .edb and some of the log files are missing than the only option is to do hard repair. Make sure you make a copy of the database before you run hard repair. Process remains the same for every exchange server version.
    325 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: