Such clusters are not Windows failover clusters, Windows clustering is
simply a resource failover technology, no application state is save at all,
and it's very hard if not impossible to do in user space code. What you can
do is keep track of of application state and maintain restore points in code
and restart at a restore point when failover occurs, this is something SQL
Server does in a MS Cluster, but here using transaction roll back, but even
then in a client server configuration you must pay attention at the client
side, a client needs to reconnect and restart the transaction when the
resource has failed over to another node.
Compare this to Tandem (now HP) Non Stop, which offers a true cluster
technology which allowes you to pick up at the point of failure and continue
processing on another node, true this is not a "poor man" cluster after
all..
Willy.
| When I played around with clustering I discovered that you can specify a
| "generic service" and the cluster will restart that service on another
server if
| the primary goes down. A true cluster-aware service would allow for more
than
| just this, however. For example, it would pick up directly where the
other
| service left off, not just restart itself.
|
| | > ok, I found, after more searches, that any windows service can be setup
on a
| > cluster, but I'm not sure I understand all the details (when their are
any
| > details attached)... does it mean that if the service uses only shared
| > resources (so it's state can be rebuild anytime) if a server fails,
another
| > one will take the relay and it will be seemless to the user, is that it?
| >
| > What we would like to do is run the service (automaticaly on windows
start) on
| > one of our server and when this server fails, the other server starts
the
| > service and take the relay... is it a behavior that can be achieved
with a
| > standard Windows Service configured in a cluster? (as I said, I'm don't
know
| > much about clusters)
| >
| > thanks a lot
| >
| > ThunderMusic
| >
| > | >> Hi,
| >> We have many servers setup as a cluster. When one server crashes,
another one
| >> take the relay... We want to know if it's possible (I suppose it is) to
make
| >> a Windows service developed with .NET 2.0 work in a cluster
environment. I
| >> mean, how to make sure the service will take the relay if one server
fails.
| >> Is there something special to do or it will work by itself? (I'm not
| >> personally used to clusters, we need it at my office and they asked me
to get
| >> the information because I'm the one who usually develop Windows
Services
| >> here, so...)
| >>
| >> thanks
| >>
| >> ThunderMusic
| >>
| >
| >
|
|
