Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2008 R2 shutdown / startup procedure Expand / Collapse
Author
Message
Posted Monday, February 4, 2013 12:58 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, December 3, 2014 3:18 PM
Points: 4, Visits: 191
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?
Post #1415465
Posted Tuesday, February 5, 2013 6:20 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 11:55 AM
Points: 6,752, Visits: 14,397
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"
Post #1415792
Posted Wednesday, February 6, 2013 2:59 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 6:03 AM
Points: 2,900, Visits: 3,301
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 2014, 2012, 2008 R2, 2008 and 2005. 18 October 2014: now over 31,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.
Post #1416351
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse