Hi Jerry,
This is kind of a common misconception of clustering. Clusting is not fault
tolerant it is highly available. Fault tolerance allows for seesion state
information to be saved and moved, high availability does not. It should
also be noted that this is not an active-active scenario, active-active
means the same group or data set is running on both nodes. The scenario
described is an active-passive/load-balanced scenario; where each node has
an active group that can fail to the other node.
When a group fails all session data is lost (this is true for all things on
clusters), essentially a failover should be conceptualized as the server
completly failing and a new server coming on with the same name. This new
server has no concept of the session state of the first server. Some
application overcome this by having a cache (SQL for example) where
uncommited changes are kept and stored on client machines or in shared
storage. When they fail-over the application knows to look for these files
and then do that work first before taking any new work. In this way a
majority, but not all, of the working data at the time of failure can be
recovered.
The bottom line is this is just how cluster works at this time, when a
cluster resource fails all session data is lost and the clients essentialy
must start a new session with a new server (even though its the same
virtual server).
--
Curtis Koenig
Support Engineer
Product Support Services, Security Team
MCSE, MCSES, CISSP
This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!
--------------------