.mdf file @ 0 bytes .ldf 6GB?

  • I have a server that crashed due to a backplane failure in a raid-5 setup. When the server came back online the .mdf file was at 0 bytes and the .ldf file was at 6GB. The really bad thing is that I don't have the data backed up with is a very bad call on me...had it set up but stopped it until our server went live and never re-activated it. Is there any way of recovering the data from the ldf file which seems to have the right amount of data for the database.

    Thanks,

    Andrew Meyers

  • andy 99843 (10/4/2009)


    I have a server that crashed due to a backplane failure in a raid-5 setup. When the server came back online the .mdf file was at 0 bytes and the .ldf file was at 6GB. The really bad thing is that I don't have the data backed up with is a very bad call on me...had it set up but stopped it until our server went live and never re-activated it. Is there any way of recovering the data from the ldf file which seems to have the right amount of data for the database.

    This is really bad situation........... you can try only if you've any full backup of the same DB and your log file is still not corrupted ...

    Options you've

    1. Log a call with microsoft

    2. Call someone whos exceptionally expert in these kind of cases.

    All the best

    Regards,
    Sarabpreet Singh 😎
    Sarabpreet.com
    SQLChamp.com
    Twitter: @Sarab_SQLGeek

  • Probably not.

    If you have no backups at all then, regardless of recovery model, the log would have been in auto-truncate mode, meaning log records got discarded after the checkpoint runs.

    There's no way (and no use) to taking a log backup as restoring a log backup has to be done on top of a database backup (which you said you don't have) and taking a log backup requires that the database is at least visible to the SQL engine (though it can be suspect)

    Try getting hold of a demo of a SQL 20005 log reader tool (ApexSQL or Lumigent) and see if it can retrieve anything. If they can, then you'll have to buy the full product to get all the data back. If not, then your DB is a loss.

    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
  • As has been said, without backups, the SQL Server route is going to be a dead loss.

    If the log reader suggestion doesn't work, then it may be worth trying some of the data recovery tools. It may just be the MFT that is corrupted, and could be recoverable with the right software.

    Before resorting to any of these recovery tools, I would recommend that you take an image backup of the entire disk first, because these tools can make things worse.

Viewing 4 posts - 1 through 3 (of 3 total)

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