June 12, 2015 at 1:46 am
Little background is necessary.
The infrastructure guys were doing some work a week or two ago and accidentally disconnected all VM's from the SAN.
Aside from the unplanned, horrible nature of the issue, i was secretly happy as it highlighted holes in our failover "strategy" i have been moaning about for a while.
On fixing the mess i found:
-anything from sql 2008 upwards was ok once storage was reconnected and the server rebooted.
-anything from sql 2005 (and/or windows server 2003) ended up with corrupt databases that needed restore from backups.
What tech was implemented post sql 2005 that may have assisted in corruption in this case?
June 12, 2015 at 2:48 pm
winston Smith (6/12/2015)
Little background is necessary.The infrastructure guys were doing some work a week or two ago and accidentally disconnected all VM's from the SAN.
Aside from the unplanned, horrible nature of the issue, i was secretly happy as it highlighted holes in our failover "strategy" i have been moaning about for a while.
On fixing the mess i found:
-anything from sql 2008 upwards was ok once storage was reconnected and the server rebooted.
-anything from sql 2005 (and/or windows server 2003) ended up with corrupt databases that needed restore from backups.
What tech was implemented post sql 2005 that may have assisted in corruption in this case?
I'm not sure that there was any tech implemented because the corruption could have been just because the databases that got corrupted were in mid-write when the storage disappeared, while other databases were idle.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply