Windows Service automatic failover

Posted on

Windows Service automatic failover – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, failover, cluster, windows-service, .

I am implementing a Windows Service. The service will be installed in a cluster of application servers.

Is there a way in the cluster functionality of Windows to set up active/passive failover for a regular Windows Service?

Or is it necessary for the service to specifically be written with calls to cluster API for failover to work?

Solution :

You can configure a generic service in the Failover Cluster Manager. These are the requirements:

  • The service or application should be stateful. In other words, the service or application should have long-running in-memory state or large, frequently updated data states. One example is a database application. For a stateless application (such as a Web server front end), Network Load Balancing will probably be more appropriate than failover clustering.

  • The service or application should use a client component that automatically retries after temporary network interruptions. Otherwise, if the server component of the application fails over from one clustered server to another, the unavoidable (but brief) interruption will cause the clients to stop, rather than simply retrying and reconnecting.

  • The service or application should be able to identify the disk or disks it uses. This makes it possible for the service or application to communicate with disks in the cluster storage, and to reliably find the correct disk even after a failover.

  • The service or application should use IP-based protocols. Examples include TCP, UDP, DCOM, named pipes, and RPC over TCP/IP.

Check out this technet article:
http://technet.microsoft.com/en-us/library/cc753938.aspx

Leave a Reply

Your email address will not be published. Required fields are marked *