Prevent automatic Failover on active/active node

  • Hello,

    I have a two node Windows 2008 cluster, for which I'm running two instances of MS SQL 2008 R2 SP1 64 Bit Enterprise Edition in an active/active configuration.

    Customer wants to run Prod in node A, and QA on node B.

    How can I configure node B or the instance that is running on node B to, if the node fails, it will NOT automatically failover to node A?

    It might seem counter intuitive, but customer says:

    "Production is critical, if the node fails, it must automatically failover to the other node, and QA should stop" (I can easily do that).

    "QA is not critical, so if the node fails, I do not want to failover automatically and potentially affect production's resources. I want to be able to manually start the instance on the other node."

    Any help is appreciated.

    Thank you

    Miguel

  • I don't have a way to fully validate this but I am fairly sure Active/Active does not allow what you want. That said you might can install a second instance on node B that is for QA database only then you get the net effect of what you want. But honestly if Production needs an Active/Active scenario I would never chance mixing in anything non-production just to save a buck, usually ends up costing more in the long run to do so.

  • MiguelSQL (3/28/2012)


    Hello,

    I have a two node Windows 2008 cluster, for which I'm running two instances of MS SQL 2008 R2 SP1 64 Bit Enterprise Edition in an active/active configuration.

    Customer wants to run Prod in node A, and QA on node B.

    How can I configure node B or the instance that is running on node B to, if the node fails, it will NOT automatically failover to node A?

    It might seem counter intuitive, but customer says:

    "Production is critical, if the node fails, it must automatically failover to the other node, and QA should stop" (I can easily do that).

    "QA is not critical, so if the node fails, I do not want to failover automatically and potentially affect production's resources. I want to be able to manually start the instance on the other node."

    Any help is appreciated.

    Thank you

    Miguel

    If you don't want QA to fail over it's simple, don't install the QA instance on NodeA. If it's already installed uninstall it 😉

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

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

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