October 14, 2009 at 12:26 pm
We recently rolled a new Win 2008 / SQL 2008 cluster into production. We've had a few instances where we've needed to failover the SQL service to the secondary node. In many cases the only way to move the node in a timely manner has been to restart the active node to force the hard failover. Wondering if anyone else has run into this and how we might avoid this. We want the failover cluster manager to work for this.
October 14, 2009 at 4:20 pm
There are 2 ways I know of and use on a daily basis to move a SQL resource between nodes.
1.) Right click on the resource in the GUI and choose move to another node (my phrasing might be wrong here but I do not have one to look at at the moment. You must make sure that all of your dependencies are correct as well.
2.) My preferred method though is to use the command line. something like the following would work.
cluster group "cluster group" /move node2 . To take to an even simpler level I have written batch files to shorten what I have to type since all of my instances are named according to patterns. So for example i have moveinst.bat which i would use like moveinst prod 1 3 - which moves my prod instance (prodsql1v1) to node 3.
The same cluster group command can be used for both the cluster group (quorum) and the msdtc resource too.
db
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply