Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Initiate Failure
- Thread starter db2nt
- Start date
The secret is in the "Resource"/Properties/Advanced.
There you have:
- restart yes/no. If restart is no, the resource after will fail one wil keep staying in failed status.
If is yes, then the next parameters will be considered:
- affect the group or not (in case of failure will force the group to bring online resources again)
- there is a threshold there. if the resource is failing more that that treshold the resource will be set to failed. If is set to affect the group, the group will also be set to failed and Microsoft Cluster will try to move it to the other node.
In the group properties, there is a failover threshold (Properties/Failover). That means that if the group will failover more than those times in that period, then the entire group will be set to offline.
Another thing is that resources are not failing over.
Just the groups are "failing over". The resource is part of the group, and will not move independetly to another group.
Gia Betiu
giabetiu@chello.nl
Computer Eng. CNE 4, CNE 5, MCSE Win2K
There you have:
- restart yes/no. If restart is no, the resource after will fail one wil keep staying in failed status.
If is yes, then the next parameters will be considered:
- affect the group or not (in case of failure will force the group to bring online resources again)
- there is a threshold there. if the resource is failing more that that treshold the resource will be set to failed. If is set to affect the group, the group will also be set to failed and Microsoft Cluster will try to move it to the other node.
In the group properties, there is a failover threshold (Properties/Failover). That means that if the group will failover more than those times in that period, then the entire group will be set to offline.
Another thing is that resources are not failing over.
Just the groups are "failing over". The resource is part of the group, and will not move independetly to another group.
Gia Betiu
giabetiu@chello.nl
Computer Eng. CNE 4, CNE 5, MCSE Win2K
- Thread starter
- #3
Gia, thanks for the info. Since I was testing "failover" I changed the groups threshold parameter and then I did an "initiate failure" on the disk resource and the group failed over to the other node. Thanks again...
Also I am planning to test websphere with cluster fail-over, how are the client connections handled ??? If the group fails over, do the connections gets re-established and how ???
Also I am planning to test websphere with cluster fail-over, how are the client connections handled ??? If the group fails over, do the connections gets re-established and how ???
I don't know how webspehere is working...
Applications in the cluster world can be:
- cluster aware
- cluster potentiall aware
- cluster unaware
A potential aware is an application that is having:
- clients are connecting using TCP/IP
- the database can have a configured location
An application cluster aware, will have their own DLLs for communicating with the Cluster, so will be aware of the cluster events.
Gia Betiu
giabetiu@chello.nl
Computer Eng. CNE 4, CNE 5, MCSE Win2K
Applications in the cluster world can be:
- cluster aware
- cluster potentiall aware
- cluster unaware
A potential aware is an application that is having:
- clients are connecting using TCP/IP
- the database can have a configured location
An application cluster aware, will have their own DLLs for communicating with the Cluster, so will be aware of the cluster events.
Gia Betiu
giabetiu@chello.nl
Computer Eng. CNE 4, CNE 5, MCSE Win2K
- Status
Similar threads
- Locked
- Question