August 22, 2013 at 8:00 am
Last weekend we applied some updates on a prod server and rebooted it. After the reboot when we connect to the server, two of the databases went to suspect mode. Later realized the log file drive got disconnected. Had to rescan the disks and reboot again in order to bring back the databases up. We want to avoid this issue in future. What's the reason behind this behavior and how to fix it ?
OS- Windows server 2008R2 SP1
SQL- SQL server 2008 sp3
August 22, 2013 at 8:57 am
Can you give us more information on this relating to the disks, are they internal disks, SAN volumes, NAS etc. Anything in the event logs of the server itself around that time too?
August 22, 2013 at 11:05 am
They are SAN drives. No info in the event logs.
August 22, 2013 at 2:24 pm
Your LUNs should be online all the time. You need to check with your SAN admin and look for possible problems. If you have a scheduled downtime window, I would test SQL. Bring it down and up gracefully and keep an eye on the LUN or disks. Reboot the server if possible.
If the SQL is running on a Cluster, test the failover. Move SQL from active node to passive and move it back.
Now, if the LUN where the Tlog file resides is down, your database won't open . That's a normal behavior. You need your Tlog file for the database to run or be fully available.
August 22, 2013 at 4:47 pm
I've had this happen to a Windows 2008 R2 server with DAS as well. I'd suggest opening a case with your hardware vendor as well just to check drivers and firmware.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply