SQL Server Performance

3 node SQL failover design question - SAN drive presentation

Discussion in 'ALL SQL SERVER QUESTIONS' started by png123, Jul 13, 2012.

  1. png123 New Member


    We are designing a 3 node SQL 2008 R2 cluster to host 2 SQL instances. I have a question on SAN drive presentation.

    Suppose we have NodeA, NodeB, and NodeC. We want to have NodeA host Dev1\Instance1 and NodeB host Dev2\Instance2. NodeC will host Dev1\Instance1 and/or Dev2\Instance2 when NodeA and/or NodeB are down. We don't want NodeA to host Dev2\Instance2; and we don't want NodeB to host Dev1\Instance1.

    Dev1\Instance1 uses only SAN drive M: while Dev2\Instance2 uses only 1 SAN drive N:

    At the OS leve, does SAN drive M: need to be presented to NodeB and SAN drive N: need to be presented to NodeA?

  2. Shehap MVP, MCTS, MCITP SQL Server

    Right , No need to present the SAN LUN M:\ to Node B and the same also no need to present the SAN LUN N:\ to node A since their relevant clusters are not planned to failover to these nodes accordingly …

    Despite of that, from SQL Server 2008 and onwards , Microsoft has added more rich powers to clustering based on Add node techniques , thereby you have a fair chance to select which node you need to add to any cluster and thus you can remove any node from any cluster without any DOWN TIME….

    This is represented at the 2 features exists at installation source "Add Node" and "Remove Node"

    Kindly let me know if any further help needed

Share This Page