October 21, 2005 at 12:04 pm
I have some SQL Server databases running off a SAN storage from 2 seperate Windows2003 servers. Last week there was a disk controller error on the SAN(this controller is shared for all servers connected to the SAN) for a few seconds.
This affected only one server which lost access to the data files residing on the SAN. The second server continued to access the files without any problems.
Both the servers are of similiar configuration and have similiar OS. What could be the reason for the difference in behavior? Is there any setting in SQL Server 2000 which asks it to timeout after a certain time when it loses connectivity to the disks? What is the default value? Please help.
October 21, 2005 at 12:23 pm
Have you tried rebooting? (The affected server, that is.)
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 21, 2005 at 12:29 pm
Look at the eventlog and see any errors related to HBA Connectivity error or warning.
October 21, 2005 at 12:30 pm
The issue was resolved after rebooting the affected server. But my question was not that.
I want to know why was only one server affected and how SQL Server behaves due to SAN connectivity issues.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply