December 4, 2006 at 9:01 am
Hi,
1) I took backup of the production database from PRODSERVER (Windows 2000) as D:\sqlserver\Backups\PROD01_db_200611172300.BAK. It is approximately 30GB.
2) In DEVSERVER I mapped PRODSERVER "D" drive share and I copied backup file locally. I copied D:\sqlserver\Backups\PROD01_db_200611172300.BAK from PRODSERVER to DEVSERVER (Windows 2000).
3) Both Production and Development are using SQL Server 2000.
4) I tried to restore PROD01_db_200611172300.BAK backup into DEVSERVER. I got following Error.
Message Banner: Microsoft SQL-DMO (ODBC SQLState:42000)
Error: An internal consistency error occured. Contact Technical Support for assistance. RESTORE DATABASE is terminating abnormally.
I found following errors in Error Log File.
2006-11-19 08:43:03.48 spid52 The backup data in 'D:\sqlserver\Backups\PROD01_db_200611172300.BAK' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable.
5) I went into Production database to verify my backup set was valid or not. I ran
restore verifyonly from disk = 'D:\sqlserver\Backups\PROD01_db_200611172300.BAK'. After 15 Min., I got result as "The Backup Set is Valid"
I did many restores in the past for the same development database from production. I never had this problem. Only difference i could think of is growing database size.
Did any come across similar situation.
Thank In Advance.
Bob
December 4, 2006 at 1:04 pm
1. I have seen the cases where restore verifyonly varified even when backup was not usable.
2. You ran retore verify on production using the copy on production.
3. Try the restore verify on Dev using the copy on the dev, during the file copy.. file might have been corrupted..
and also run the restore headeronly command to check the backup details..
MohammedU
Microsoft SQL Server MVP
December 4, 2006 at 2:39 pm
Attentions should be also paid to
1. If the restore order is correct?
2. If the restore file paths are the same as the original data file paths?
...
December 5, 2006 at 7:48 am
If you lookup RESTORE VERIFYONLY in BOL, the first paragraph states:
Verifies the backup but does not restore the backup. Checks to see that the backup set is complete and that all volumes are readable. However, RESTORE VERIFYONLY does not attempt to verify the structure of the data contained in the backup volumes. If the backup is valid, Microsoft® SQL Server™ 2000 returns the message: "The backup set is valid."
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply