July 17, 2008 at 11:59 am
I have several databases on EMC SAN drives. Each time I reboot the server, these databases can't come up since the drives on the SAN storage are not available yet. However, after the reboot I log on to the server and re-start SQL 2005 Server service then all databases come up normal.
Is there a way to configure a delay to startup these databases?
Thanks for your help.
Hien Doan
July 17, 2008 at 12:11 pm
You should contact your SAN vendor. This is something they should have taken care of for you.
July 17, 2008 at 12:18 pm
We purchased EMC through Dell and I have talked to them a few times. There is no solution at this time from their side.
Hien Doan
July 17, 2008 at 12:33 pm
I find that hard to believe. This would seem to be a bit of a widespread problem for them and it would impact more than just SQL Server.
July 17, 2008 at 1:57 pm
Check your SQL service account running under.
Run it as a network user and not the Local System account.Then it will have access to the network.
see if this is the issue.
Maninder
www.dbanation.com
July 17, 2008 at 3:07 pm
I would push a bit harder with the vendor. Theoretically (I would not do this) you can run the OS on SAN storage so, if they are accepting this as being the norm, it goes against the SAN vendors standard that they put forth. I have used EMC storage for years and have NEVER had this issue so, there has to be something else going on.
One thing to consider is seeing if there are updated drivers for the HBA cards that you are using.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
July 17, 2008 at 4:03 pm
Maybe you can find a service that you can make SQL server service(s) dependent upon? I've never had this exact problem, but have worked around similar problems by adding a service dependency (in services.msc). The trick would be to find a service that doesn't finish starting up until the SAN drives are available.
July 21, 2008 at 10:01 am
I would like to thanks everyone who responded to this request. We upgraded Microsoft iSCSI to the latest version 2.07 and it seems the server starts up much faster. It took almost 10 minutes to reboot the server under 2.06 version.
The databases on the SAN drives still fail to mount since the drives are not available. We put SQL Server service in Manual and write a script to check for the SAN drives, once they are available then SQL Server service is started.
Not perfect but it's workable.
Hien Doan
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply