| Author |
Topic |
|
admin001
Posting Yak Master
166 Posts |
 Posted - 2003-07-11 : 22:28:20
|
| Hi ,Recently i came across two issues which I would like to share :1.) We have a Disaster recovery server which holds approx. 80 Databases . We are daily copying the bak files to the DR server and try to restore the DB's whenever weplan a BRP . This is temp solution as I have thought of Log Shipping as a high Availiability plan . The problem I am facing now is :When I try to restore the DB from the Bak file on the DR server , for some of the databases , it gives me an error that An Internal Inconsistency has occured . Contact your system administrator . What I have seen is the database are getting on a single drive . So does this affect the restore process ? This occurs specially for large DB's with around 2.5 GB . 2.) And for some databases , the row count differs from the Production SQL server although all data seems to be there . Is it because of database schema or the transaction log that is different on DR server after restore . I am unable to figure out these two issues . Need some insight on this pl . Thank you very much . |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-07-12 : 15:05:08
|
| >> the row count differs from the Production SQL server although all data seems to be there.How can all the sata be there but the row counts be different?Are you using sysindexes to get the rowcounts? Maybe it is inaccurate and you need to run dbcc updateusage.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
admin001
Posting Yak Master
166 Posts |
Posted - 2003-07-13 : 22:48:30
|
| Hi nr ,Thanks . I am just using a select statement ( select * from tablename ) randomly to see if all the data is there on the DR server . In that, I just compared the row count from the Prod. server . Thanks once again . |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-07-14 : 12:57:43
|
quote:
What I have seen is the database are getting on a single drive . So does this affect the restore process ? This occurs specially for large DB's with around 2.5 GB .
2.5GB is not a large database. How long do these restores take? For database that I have restored that are around the same size, it should take about 5-10 minutes. quote:
And for some databases , the row count differs from the Production SQL server although all data seems to be there . Is it because of database schema or the transaction log that is different on DR server after restore .
What do you mean the database schema is different on the DR server? They will be identical after the restore. Also, the transaction log doesn't have an effect on the row counts. When you compare the row counts, are you taking into account that production is being updated (assuming that customers are using the production server) so the row counts will not be exact but they probably will be close.Tara |
|
|
|
admin001
Posting Yak Master
166 Posts |
Posted - 2003-07-15 : 02:54:57
|
| Hi ,You are right as the production data is always being updated and hence the row count differs . But I am little worried about that Internal Inconsistency error . When i click on OK to restore , it takes 10 min. to display this error message . Can it be due to some hardware ? But at the same time , my small DB's are getting restored in no time . Its only for the DB's more than 1 GB size . I think the restore too should happen on different drives rather than one single drive at the moment . Do you think so ..Thanks |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-07-15 : 12:52:26
|
| If you want the restore to use multiple drives then you will need to use the WITH MOVE option in the RESTORE command.RESTORE DATABASE DBNameFROM DISK = 'E:\MSSQL\BACKUP\DBName.bak'WITH MOVE 'DBName_Data' TO 'F:\MSSQL\DATA\DBName_Data.mdf',MOVE 'DBName_Log' TO 'G:\MSSQL\DATA\DBName_Log.ldf',REPLACE, STATSHow often do you get the inconsistency error? It takes 10 minutes to pop up the error because the problem is 10 minutes into the backup file. You might want to add the verify option on the backup so that you know if the backup is valid.Tara |
|
|
|
admin001
Posting Yak Master
166 Posts |
Posted - 2003-07-18 : 06:01:14
|
| Hello ,Thanks for all your help . Finally I was able to restore the big Database and get rid of that Internal Inconsistency Error . I tried restoring the DB's on different drives and it worked . I think eventually I will keep all the databases on two drives so that I have no further problems . Thank you once again. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-07-18 : 12:35:41
|
quote:
I think eventually I will keep all the databases on two drives so that I have no further problems .
You can restore a database on one drive without any problems. The fact that you are having problems doing it this way leads me to believe that you've possibly got a hardware problem. I would definitely look into this.Tara |
|
|
|
|
Restore Database .