Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a SQL Server (2008) on a Windows Server (2008) VM that has iSCSI targets on a SAN. When the connection is lost between the VM and its disks the OS is able to reconnect to the targets but SQL does not "find" them again; the service needs to be restarted. Is there something that I'm missing that would make the OS report to the service that the targets have been reacquired and, thus, no longer need to be restarted?

share|improve this question
I'd fix the SAN availability problems before trying to re-engineer application fault tolerance. – Chris S Jul 27 '10 at 18:37
+1 to Chris's comment. Fix the problem at source. – user3914 Jul 28 '10 at 5:36
Are your system database on the iscsi LUN ? is this a stand alone or clustered instance? – Nick Kavadias Jul 29 '10 at 11:44
up vote 1 down vote accepted

Best option is to fix iscsi so you don't lose your LUN's. Your at risk of corrupting your databases.

My guess is SQL Server is crashing because it's losing it's system databases. move the system databases to a local disk & it will stop sql server crashing. You can leave your user databases on iSCSI at your own risk, but sql server should survive losing the user databases.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.