SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server 2008 R2 shutdown / startup procedure


SQL Server 2008 R2 shutdown / startup procedure

Author
Message
Mike.Dougherty
Mike.Dougherty
Forum Newbie
Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)

Group: General Forum Members
Points: 8 Visits: 199
I have a SQL Server 2008 R2 2-node cluster running Windows Enterprise 2008 R2 and SQL Server standard Edition 2008 R2 using iSCSI attached NetApp storage. When either node is rebooted, a failover occurs normally and everything works accordingly. We recently needed to do some UPS upgrades on our server room and we took both nodes in the cluster down. Upon startup of node1, I noticed the cluster wouldn't come online and that in DISKPART, the iSCSI luns were set to RESERVED. I launched the Microsoft iSCSI initiator, and I was able to see that the targets were connected and the volumes were mapped. Because the WITNESS disk is one of those LUNs, the cluster wouldn't come online. I started Node2 and went into the iSCSI initiator and did a refresh on the target, and the LUNs then came online. I am not sure if it was the startup of Node2 or the refresh of the iSCSI initiator target that caused the disks to become available. So my question, is this normal behavior for having 2 nodes in a cluster shutdown down?
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)

Group: General Forum Members
Points: 54111 Visits: 17681
can you post results of the following when run from a command prompt on one of the nodes

cluster /quorum



-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
EdVassie
EdVassie
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14042 Visits: 3901
I have seen similar situations, particulary on my sandbox clusters.

There are a few ways to safely shut down a cluster, and a few that can cause problems.

Safe methods:

a) Shut down each node one by one. Wait until all passive nodes have completed shutdown before shutting down the active node. On restart, start the previously active node first.

b) Shut down SQL by putting the cluster offline (CLUSTER ClusterName RESOURCE GroupName /OFF) before you shutdown any nodes. After restart put the cluster back online, which will restart SQL.

Unsafe methods:

a) Stop SQL Server with NET STOP or similar. Almost always causes a problem.

b) Shut down all nodes at the same time. This can cause a problem if some objects complete their failover before the active node shuts down, leaving other objects still on the active node. However, on a power failuer everything gets killed at once so this should not give a problem at restart.

My recommendation is to build a sandbox cluster, then run some scenarios that could break it, and when it is broken work out how to fix it. Unless you have destroyed some data, just about all broken clusters are can be fixed, even if you have to eject nodes and add them back in again.

Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search