Re: How to make C#.net Windows Service be programmed to run on only ac

"Shuchi" <agarwalshuchi@xxxxxxxxx> wrote in message news:86d2c9b6-543c-46ad-8523-bc3d60e43f48@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for responding.

My Windows Service executes jobs ( DTS or SQL serbver jobs ) that are
required to run in a specific order in SQL Server. This is defined in
a sql table.
Only one instance of service is required to run at one point of time
on the active cluster node. If its 2 instances run at one point of
time, one on active and other on passive then it executes each job in
queue 2 times. It is basically a process queue executer service.

I would not want only one instance to run on active node and another
instance in case ( on passive ) is running should either do nothing or
should stop.

It would be good that in case of a fail over the service stops on the
active node that has failed and starts on the passive node and then
the passive node becomes active..and so on.

Thanks again.
Shuchi.


All "Windows Services" can be registered as a generic cluster resource in MSCS. In such scenario, your service can be active on one node, and be failed-over to another node either by a node or service failure of the active node/resource, or manually by means of a user action. The problem is that your service must be implemented as such that it handles "restart points", that is you need to keep track of the tasks states, so that you can restart a task where it was left off by at the moment of fail-over.


Willy.



.

Relevant Pages