Post reply

How to stop the SQL Virtual server (SQL 2008 R2) services without failover?

  • November 9, 2010 at 7:31 am

    #240927

    I have configured the 2 node cluster on Windows 2008 Server and Installed SQL Server 2008 R2 Virtual server in it and it is highly available now.

    Now, I want to do the Instance (SQL Virtual server) level recovery; basically we need to restore all the user db's including system db like Master, temp etc. In order to restore the Master Db we need to stop the MSSQLSERVER service. But whenever I try to stop the service in the active node the service is getting started in the other node (i.e. Owner ship of the Virtual Server is getting moved from one to other node) as because I configured the failover cluster.

    I want to know how to stop the services without failing over to the other node in order to do the Instance level recovery of the Virtual server.

    Thanks,

    Elango C

  • November 9, 2010 at 8:46 am

    #1248354

    you will need to disable the instance in your cluster resource group.

    Once disabled you can then stop the service without any failover (as the resource is disabled)

  • November 9, 2010 at 10:45 am

    #1248448

    Using Cluster Administrator, go to the resource group for the SQL Services. Right-click "SQL Server", and select "Take Offline". This will also take the SQL Server Agent offline.

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes

    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • November 10, 2010 at 8:28 am

    #1248922

    For Windows 2008 Clusters, Go to Failover Cluster Manager, Under the Virtual Cluster Name open Services and Applications, under that select your virtual SQL Server, Take a look at the resources underneath of that and take the service offline the way Wayne suggested.

    You will want to pause the other node or take it offline to prevent an accidential failover from occuring.

    2008 clustering is a little more distributed and if you are recovering your system DB's you'll want to stay on one node.

    Just to be sure this get's asked, are the databases your restoring comming from a clustered server, or are you migrating?

    Twitter: @SQLBalls
    Blog: http://www.SQLBalls.com
    Channel: https://www.youtube.com/@Tales-from-the-Field

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply