I am hoping that some one out there has seem this behaviour and can point me in the correct direction to solve.
We have just built a new Windows 2008R2 server on HP Proliant DL380-G5, with SQL 2008.
We are using iSCSI to connect to our FAS30370, via a seperate iSCSI network.
NetApp Host utils are 5.3
Snap Drive is 6.2
When the server is restarted we recieve error message that SQL can not find the SQL databases.
If we then manually restart SQL , every thing if fine.
If we place "persistant" targets in the Microsoft iSCSI initiator, SQL starts just fine , BUT know SnapDrive has become all bitter an twisted , is failing to enumerate LUNs, and no drives or iSCSI information show up under the SnapDrive MMC.
IF we now restart the SnapDrive Service every thing is happy.
We are trying to get a combination that works 100% from BOOT for both SQL and SnapDrive.