missing .mdf and .ldf database file after hard drive crash

  • hwp (3/24/2014)


    Hi All,

    Thank you for the reply. The hard drive that crashed was actually the DATA drive.

    And the backup is corrupted as well, plus it is a .bak file. It doesn't have .mdf and .ldf file.

    Sorry, a total noob here.

    Thanks,

    Howard.

    First of all, Moden is right. STOP EVERYTHING and get to an expert. You could accidentally destroy data without knowing it. Do you need references for good experts?

    As Gail said, you may need a data recovery company. www.gillware.com is the best at the most reasonable prices. Beware that the company may not be able to resolve a crashed drive to the point of finding anything you can use.

    In the future, if you recover:

    1. Back up your database daily to a NAS or other destination that is not the same physical media as your MDF or LDF file. If the data are critical, use full recovery model and back up the transaction logs every 5-30 minutes, to that separate location.

    2. A second stage backup should be taken DAILY of that NAS to tape or the cloud or somewhere. What if the NAS fails too?

    3. Test restores should be done at least monthly to another location to ensure backup integrity.

    There is nothing more traumatic to a DBA than the total loss of a database. I hope and pray that you can recover!

    Thanks

    John.

  • hwp (3/26/2014)


    Thank you very much for all the recommendation and suggestion.

    We are currently looking for expert help in recovering our database. If anyone has any suggestion or do provide service please PM me.

    We are located in Los Angeles.

    Thank you,

    Howard.

    Hi. The best SQL people that I can recommend are Paul Randal and Kim Tripp. See www.sqlskills.com. They do DR like this.

    Thanks

    John.

  • @john-2,

    Thank you for the recommendation, we will contact them for the recovery of the database.

    Thank you,

    Howard.

  • Two things.

    They're not hard drive recovery specialists. If you don't have an mdf and an ldf which doesn't attach or a backup which won't restore (a full-sized backup, not the 20k one you have), don't call them. Contact a drive recovery company instead.

    They are not cheap and recovering a database is not quick.

    To be honest, unless the data in this lost database is worth hundreds of thousands of dollars, I'd be looking at restoring that old backup that you have. At least then you'll have something, not the nothing that you've had for a week now.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • GilaMonster (3/28/2014)


    Two things.

    They're not hard drive recovery specialists. If you don't have an mdf and an ldf which doesn't attach or a backup which won't restore (a full-sized backup, not the 20k one you have), don't call them. Contact a drive recovery company instead.

    They are not cheap and recovering a database is not quick.

    To be honest, unless the data in this lost database is worth hundreds of thousands of dollars, I'd be looking at restoring that old backup that you have. At least then you'll have something, not the nothing that you've had for a week now.

    I was referring him to Gillware.com for the hard drive. As for SQL best practices and DR if the backup is at least in part recoverable, I recommended SQL Skills. Sorry if my note was ambiguous.

    Thanks

    John.

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply