Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


databases reads inconsistency I/O error


databases reads inconsistency I/O error

Author
Message
riyasriy
riyasriy
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 16
Hello,

Recently I faced a BSOD in my windows and I have reload the OS. All the SQL databases are gone since the C: drive is formatted. Once I re-installed OS, SQL server I created databases with the help of .bak of all my databases. However the most of databases are unable to be restored and gives IO inconsistency error. Some of them are restored with the same error specified. And finally the problems are somewhat settled with huge data loss. My question is
1. What is the best backup strategy for MSSQL such that after re installation of SQL server, the databases must be as before it was crashed with all permissions with minimal time.
2. What causes the IO error. I google it but could not get an accurate answer for what I am searching.

Note: I just back up my user databases and not the master file database. What does the master file do and does it have effect while restoring the database.

Any help/ideas will be highly appreciated.

Regards,
Riyas
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47299 Visits: 44392
1) Depends on your downtime and data loss allowance (RTO and RPO SLAs). In short, you need a backup strategy that will allow you to meet them. Find out what they are, then start designing.
Backup the system databases. There's all sorts of things in the system DBs that you don't want to be losing (logins, linked servers, jobs, job history, etc)
Run consistency checks often. When the DB is corrupt is too late. You need to know if you're backing up corrupt databases.
Test your backups. Restoring a backup is the only way to be 100% sure it will restore
Save the backups somewhere else. A backup stored on the same drive as the data file is a waste of space.
Test your recovery strategy.

2) Could have been anything in the IO stack. Buggy IO drivers, misbehaving filter driver, faulty hardware.


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


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search