RE: Cluster Configurations

Thanks for the Input :).

Your right never thought about the other duplicates that are already there.
Much appreciated.

--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
http://sqllearnings.blogspot.com/


"Linchi Shea" wrote:

With an 8-node cluster, you may save some money on having fewer servers doing
nothing. But you have increased complexity and have to deal with the
scenarios where multiple instances fail to the same node. The issue here is
HA, not load balancing. As such, it's best to consider, for instance, a
2-node failover cluster as a single server that has built-in redundancy for
your database. Just as you should use multiple HBAs and multiple NICs in a
server, and never consider the extra NICs/HBAs as doing nothing, it's simply
the cost of doing business if the business requires it.

Linchi

"Mohit K. Gupta" wrote:

I see; is there any advantage of creating a 8-Node cluster in SQL server then?

The only thing I can think of is if we go 2-node configuration with the 8
servers, we have 4 severs doing nothing. Well they are there for the HA; but
I think we decided the 8-node configuration to better use the hardware.

Maybe a 3 node configuration will be enough with (active-active-passive)?
So it doesn't seem like as big of a waste? What you think?

Thanks for the comments :)

--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
http://sqllearnings.blogspot.com/


"Linchi Shea" wrote:

Sounds reasonable to me. But taking a step back, you have to ask yourself
what you are trying to accomplish with this setup. I've had experience with
multi-node multi-instance clusters and two-node single-instance clusters.
Personally, I think you've put too many things into one basket with a
multi-node multi-instance cluster. For HA, I think you are better offer with
two-node clusters.

Linchi

"Mohit K. Gupta" wrote:

Thanks for reply; if I may ask will those the following configuration seem
sound to you for 8-Node Cluster with 6A-2P.

Node 1: Default Instance -> Failover to Node 4
Node 2: Named Instance -> Failover to Node 4
Node 3: Named Instance -> Failover to Node 4
Node 5: Named Instance -> Failover to Node 8
Node 6: Named Instance -> Failover to Node 8
Node 7: Named Instance -> Failover to Node 8

So in worst case Node 4/8 could each have 3 instances running if everything
fails,

Thanks again for help.

--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
http://sqllearnings.blogspot.com/


"Linchi Shea" wrote:

No, you cannot have two default SQL Server instances in the same cluster. So
your configuration A doesn't work.

Linchi

"Mohit K. Gupta" wrote:

Hi,

We are currently looking at setting up 3-Node Cluster with
Active/Active/Passive configuration. I am sorry clustering is my weakness
and I not very good at it, so if the question sounds wrong please let me know.

Configuration we are aiming for (Configuration A):
Node 1: Default Instance (SQL2005) and Named Instance (NI01)
-> Set to Fail Over to Node 3
Node 2: Default Instance (SQL2005) and Named Instance (NI01)
-> Set to Fail Over to Node 3

Configuration I was thinking we should do (Configruation B):
Node 1: Default Instance (SQL2005
-> Set Fail Over to Node 3
Node 2: Named Instance (NI01)
-> Set Fail Over to Node 3

Could someone please tell me if Configuration A is possible? Or do we have
to choose Configuration B as main route?

Thanks.

--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
http://sqllearnings.blogspot.com/
.

Relevant Pages

  • RE: Active Directory Group in SQL Server 2005 SP3 Server
    ... MCITP: Database Administrator ... MCTS: SQL Server 2005 ... "Mohit K. Gupta" wrote: ...
    (microsoft.public.sqlserver.security)
  • Re: SQL native client
    ... "Mohit K. Gupta" schrieb im Newsbeitrag ... i have a VB6 app which connects via SQL native client 2005 to a SQL Server ... As other computers don't need admin rights i think it's a config. ...
    (microsoft.public.sqlserver.clients)
  • Re: SQL Server Named instance with Default Instance
    ... There should be no problem with a default instance and a named instance. ... instance to SQL Server. ... "Mohit K. Gupta" wrote: ... > SQL DBA team install named instance on the cluster enviornment. ...
    (microsoft.public.sqlserver.clustering)
  • RE: SQL Agent not Showing in SSMS
    ... "Mohit K. Gupta" wrote: ... MCTS: SQL Server 2005 ... Agent node disappears on NodeB but is still visible on NodeA. ...
    (microsoft.public.sqlserver.security)
  • Re: Too many full-text columns or the full-text query is too compl
    ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ... "Mohit K. Gupta" wrote: ...
    (microsoft.public.sqlserver.fulltext)