hr_sea
asked on
MSSQL: Data recovery or force restore?
I need to restore my sql server from backup. Normally no problem, however my last full backup filled up the disk before it finished thus that backup is no good. The subsequent differentials ran OK. However I'm in a situation where the database blewup and I need to restore.
My situations.
Week 1 - successful full
week 1 - successful differentials
week 2 - failed full
week 2 - successful differentials
end of week 2 - database crash - need to restore.
I see to not be able to apply the successful differentials from week 2 to the full from week 1. I suspect it thinks the full from week2 was successful and differentials are from the point? "Cannot apply the backup on device '<file>' to the database '<database>'" is the message I get.
At this point we're not concerned about consistency, we just want to get raw data back to re-insert into a new database. Is there a way? Just to see raw tables, csv, tab delimited or anything would be fine. Or better yet, apply the week2 differential to the week1 full. Am I just SOL?
My situations.
Week 1 - successful full
week 1 - successful differentials
week 2 - failed full
week 2 - successful differentials
end of week 2 - database crash - need to restore.
I see to not be able to apply the successful differentials from week 2 to the full from week 1. I suspect it thinks the full from week2 was successful and differentials are from the point? "Cannot apply the backup on device '<file>' to the database '<database>'" is the message I get.
At this point we're not concerned about consistency, we just want to get raw data back to re-insert into a new database. Is there a way? Just to see raw tables, csv, tab delimited or anything would be fine. Or better yet, apply the week2 differential to the week1 full. Am I just SOL?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
(disclaimer: I'm not a sql expert so my terminology may be wrong)
An update statement which changed all the values in one field (column) was executed. Our "dba" was not using transactional updates (?) so could not roll back the action.
So, I guess what I'm seeing is that any differential after any sort of incomplete full is worthless.
Yes. A differential is based on the changes of the last full backup (whether or not it was successful) - because your full backup failed, then the differentials based on it are useless.
Your terminology is fine - it sounds as if your dba ran an update statement without the WHERE clause. He is not the first one to do that or the last.
Your terminology is fine - it sounds as if your dba ran an update statement without the WHERE clause. He is not the first one to do that or the last.
ASKER
Yes, our dba ran and update without the WHERE. I know it happens! Thank you!
if you are dependend on backup than the only way is what ptjcb suggested.