Chuck Timon [MSFT]
Guest
|
Posted:
Wed Sep 28, 2005 8:51 pm Post subject:
Re: Cluster fail over behivor |
|
|
By default all cluster resources have each node in the cluster as a
'Possible Owner' for the resource(s). As long as this is not changed,
resources from a failed node should failover and come online on another
available node provided the available node has not been 'Paused'. Now,
multiple Exchange virtual servers running on a single cluster node is only
supported in a 2-node cluster. Once the number of nodes increases beyond 2,
the clustered Exchange model transitions to an N+1 model. So, if there were
two Exchange virtual servers on a 3-node cluster and two of those nodes
failed, one of the EVS' would not come online. SQL does not have that
model, but SQL 2000 is only supported on a max 4-node cluster. Eight node
clusters will not be supported until SQL 2005.
--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
"Oren Zippori" <orenzp@hotmail.com> wrote in message
news:OcHWn1DxFHA.464@TK2MSFTNGP15.phx.gbl...
| Quote: | Hi,
I have a question regarding a 2003 cluster behavior, what will happens in
a scenario where I have 2 nodes in the cluster:.
Node1 - holds the cluster resource (quorum) and exchange resources
Node2 - holds the SQL resource only.
what will happened if node 1 fails? is the SQL resource on node one
suppose to go off line until the cluster resource it self goes back online
on node2?
I had that exact problem and after half a minute the SQL was back online.
Thanks in advance
Oren Zippori
|
|
|