Question : Failover Policy for MSCS 2008 + SQL Server 2008

Everytime I bounce my primary node in my 2008 cluster, the cluster fails over to the secondary node.  How can I stop this?  Also since it is SQL Server 2008 Cluster on top of MSCS 2008, do I need to set the policy on both levels or will the MSCS 2008 policy take care of it.  

Basically I do not want the cluster to failover when a patch is installed and reboot is required.
Also, when the cluster does failover, how do I get it to failback?  Is this just on the MSCS side or the SQL Server side as well?  Thank you for your help.

Answer : Failover Policy for MSCS 2008 + SQL Server 2008

Look at http://blogs.msdn.com/clustering/archive/2008/05/10/8483427.aspx - there is a list of useful documents related to clustering.

Your SQL has to move to secondary node! It's why you created a cluster... If you like to control entire process manually you can take your SQL resource offline (in failover cluster management console) then do your normal maintenance task and then bring it online again (after ensuring it is located on a right node).

Failback options can be set in group properties. failback is disabled by default because failing back generates next service availability break.