 | |
Node and Cluster
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#61
 
| |||
| |||
|
Thanks. -
11-28-2008
, 12:47 PM
|
The cluster is the overall management entity. It manages member nodes and instances. You install a SQL instance to the cluster and can designate which nodes are allowed to run that instance. For ease of management, I would set up all three nodes for each instance. I would then place instance 1 on node 1, instance 2 on node 2, and leave instance 3 open for first failover. During maintenance windows I can move instances around so that I can reboot nodes as necessary without affecting end users. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Lijun Zhang" <sonyzhang00 (AT) yahoo (DOT) com> wrote in message news:eZ9nQpAUJHA.584 (AT) TK2MSFTNGP06 (DOT) phx.gbl... So if I install two instances of SQL Server on one cluster that contains three nodes (N1, N2, N3), I can configure that one instance run on N1, and another instance run on N2, and both can failover to N3 when necessary, right?. Sorry I am new to windows cluster. We currently have two very heavily used SQL Server instances running on two separate servers. We plan to move on to failover clustering. It is not an option to put the two instances on the same server due to the load the server. I hope we can get some guide for the planning. My main concern is do we need to buy two new nodes and setup separate cluster for each instance? or buy one would be enough? Thanks. "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:%23p34vg9TJHA.5268 (AT) TK2MSFTNGP04 (DOT) phx.gbl... Instances and nodes are independent. You can move instances between nodes at will. You can have instances on different nodes. Note that each instance must have its own disk(s), IP address, and network name. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Lijun Zhang" <sonyzhang00 (AT) yahoo (DOT) com> wrote in message news:O6DtNb9TJHA.5404 (AT) TK2MSFTNGP03 (DOT) phx.gbl... So if N1, N2, and N3 are configured to one cluster, and if we use more than one instance on that cluster, at any moment, all instances will be run on one node, right? You can not have one instance run one node and another instance run on a different node on the same cluster, right? "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:Oyz4U68TJHA.1164 (AT) TK2MSFTNGP02 (DOT) phx.gbl... No. A node can only belong to one cluster at a time. You can use named instances to get more than one instance per cluster. You can also use DNS aliases to set up short name connections. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Lijun Zhang" <sonyzhang00 (AT) yahoo (DOT) com> wrote in message news:uvWvCc1TJHA.1164 (AT) TK2MSFTNGP02 (DOT) phx.gbl... Can one node be configured to belong more than one clusters? For instance, if we have three nodes: N1, N2, and N3, can we configured N1 failover to N3, and N2 failover to N3? Both N1 and N2 has their own default SQL server instances. Thanks for any input. Lijun |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.