| Author |
Topic |
|
anupkumars
Starting Member
2 Posts |
 Posted - 2004-08-17 : 00:09:10
|
| Hi all,We are having backups of seven production databases from one of our clients. They have taken the backup and sent it for configuring here at the development center. The database size is pretty big (47 GB, 45 GB, 25 GB, 360MB and so on). We were able to restore the smaller databases. But for the bigger ones, we are facing a problem. We are getting Interbal Consistency error when restoring. We talked to the client. They informed us that, they were able to restore it from this backup files. Please help me out in soriting this issue. Is it becuase of the system configuration? At the client site, they are using high end servers. But we are testing it with Desktop servers. Any RAM problems or something like that? Because we were able to restore the smaller databases...We tried the SP_HELPSORT and compared the results from the client SQL Server installation and ours. Both are same. Please let me know, if anybody has got a solution for this "Internal Consistency Error"Thanks and RegardsAnup |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-08-17 : 00:13:36
|
| What OS version/SP and SQL Server version/SP are you running? What are they running?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
anupkumars
Starting Member
2 Posts |
Posted - 2004-08-17 : 00:29:13
|
| Hi there,We are running Windows 2000 Advance Server/SP Version - 4 Build 2195/Hot Fixes SP5SQL Server 2000 Ent. Edition/SP Version - 3. I am not sure abt the versions our client is using.Thanks and RegardsAnup |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-08-17 : 06:39:38
|
| Do you have any more detailed errors messages? e.g. from the SQL Server logKristen |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-08-17 : 07:23:54
|
| Try running:RESTORE VERIFYONLYFROM DISK = 'd:\backup\backupfile.bak' --Replace with the appropriate backup fileand see what you get with that. Also, have the client run a DBCC CHECKDB on the databases.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-08-17 : 12:17:19
|
| How were the files sent to you? It's possible that the larger ones became corrupt during that process. You might want to ask the client to send you the files again.Tara |
|
|
|
ajthepoolman
Constraint Violating Yak Guru
384 Posts |
Posted - 2004-10-12 : 15:20:48
|
| I know this topic is out of date, but for what it's worth, our BAK file was corrupt which caused the internal consistency error.Aj |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-10-12 : 15:46:47
|
| What a right royal pain ... I suppose I would have expected SQL to use some sort of checksum in the backup file so that it could detect a corruption :-(Mind you, even the government can't detect corruption ...Kristen |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-10-12 : 18:26:43
|
| SQL Server does do that though if you tell it to. It can detect whether or not it is a valid file. But that doesn't mean that it's restorable. That's why you must test your backups regularly.Tara |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-10-12 : 18:33:06
|
| Would that be the "RESTORE VERIFYONLY" command, or is there some further magic?Kristen |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-10-12 : 19:35:13
|
| Yes that's it. I never run that command though as we test our backups regularly. Testing your backups is the best way to know if the file is restorable. RESTORE VERIFYONLY just "checks to see that the backup set is complete and that all volumes are readable."Tara |
|
|
|
pyeoh
Starting Member
18 Posts |
Posted - 2004-10-12 : 21:53:28
|
| You and your client could use a file checksum generation utility to check the consistency of the backup files. We have a fast (and free) MD5 utility to do just that. If it's any consolation, SQL2005 appears to have an option to generate checksums for backups.Peter Yeohhttp://www.yohz.comNeed smaller SQL2K backups? Use MiniSQLBackup Lite, free! |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-10-13 : 12:25:24
|
| That doesn't mean it's restorable though.Tara |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-10-13 : 13:14:58
|
| I think it would be good to know that the backup file that was actually created hasn't changed since - one less thing to waste a day trying to solve. There, that's me done; I'll check the pigs are fed and ready to fly ...Kristen |
|
|
|
carago
Starting Member
1 Post |
Posted - 2005-01-28 : 16:50:46
|
| Hi, maybe it´s too late but I´ll try to help.I have experienced a problem like this with a database on a server running Windows 2003 and SQL 2000 and it has been solved just yesterday when I dropped some tables with strange names, such as: CAAI04, CAAI07, MOVIM, etc. that were imported when the database was built.These names might be reserved names to SQL Server (I think).Rago |
|
|
|
|
DB Restoration (Internal Consistency Error)