November 22, 2007 at 10:23 pm
Hi,
I am in a very rough situation and would like some help/advise.
My server crashed and I lost everything. Server was rebuilt and I tried to restore the .BAK file from tape. Noticed that backups were not going good as well. I found one .BAK file but when I restored it is reporting to be approx. 200Kb smaller than the size reported by windows. Backupexec restored 20785192 bytes but the size of the restored file is 20983171 bytes.
Anyway, when I try to restore .BAK file from enterprise manager system just sits there for hours. and when I check the file it is reporting as corrupt/incomplete.
Can anyone suggest any way to get data out of this file?
It is a really bad situation. I will be calling MS tomorrow but any suggestions are welcome.
November 23, 2007 at 12:03 am
SQL 2000 or SQL 2005?
If you have a SQL 2005 server around (even if its just a desktop) try out the RESTORE DATABASE ... WITH CONTINUE_AFTER_ERROR
It's new functionality in SQL 2005 that allows a partial restore of a corrupt backup. You won't have everything, but you'll probably have more than you do now.
If that succeeds, bcp the data out and script out what objects you can
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
November 23, 2007 at 9:05 am
Thanks for the quick response. I will give it a shot right now
November 23, 2007 at 9:10 am
Will a trial version work?
November 23, 2007 at 10:53 am
Oh, I forgot to mention that yesterday I used force restore and I manage to recover MDB and LDB files but I got some messages like bypassing recovery etc. around 90%. I have the MDB and LDB files but I cannot connect to the database
November 24, 2007 at 5:38 am
Is that on SQL 2000 or SQL 2005?
What's the state of the database? (suspect, recovering, offline, ...?)
There may be a way, but just so that you can copy the data out. Won't fix it.
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
November 24, 2007 at 10:52 pm
It is SQL 2000
I managed to bring the database in Emergency mode and have started to recover the data table by table by transfering the data.
Some tables are not transferring over as they are corrupt but I am trying my best to get whatever I can.
I am not sure if I can recover damaged tables or not? Any Ideas?
November 25, 2007 at 11:59 am
Probably not. What errors are you getting when trying to select from the tables?
If it were a corrupt DB, there might be a chance or reading the pages raw and decoding them by hand. Is really time consuming and requires a great deal of experience. Since the backup that you restored was corrupt, the data probably isn't there at all.
What did MS's product support say?
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
November 25, 2007 at 7:34 pm
I managed to recover almost all of the 243 tables except for 8. These 8 tables have a lof of images and I am having difficulty restoring those.
I called microsoft on Fri and opened a case but have not heard back from anyone yet.
November 26, 2007 at 4:57 am
I take it you don't have any previous backups (to the one you're currently using) that might have these 8 tables on it?
There are some disk recovery services that might be able to pull the data you need from the server's old hard drive, but I don't know what the cost would be. Look in your local yellow pages under Data Recovery or Computer-Service & Repair.
January 2, 2008 at 10:24 am
Thanks a lot for everyones Help and Answers. I managed to recover most of the data by opening the database in emergency mode. I did loose some but I guess it is better than nothing.
April 30, 2012 at 3:29 am
Corruption in SQL server or SQL database backup files are mostly observed by crash in SQL server. May be it is the same case with you, in these conditions you can't repair your database easily but some application managers are there for your convenience. SQL BAK File Recovery tool is the best solution for this problem. More reference can be taken from: http://sqlbakrepairtool.webs.com/[/url]
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply