Multiple instance of CRM Async service running in SQL Server Windows Fail Over Clustering

(0) Share

Report

Posted on by Community Member

How should we install and configure CRM Async service in a Clustered SQL Instance (Windows Fail Over Clustering) so that only one instance of Async services should run on an Active/Passive node. While I move the node, I want to automatically run the async services installed in Sql Node 2. ie. When SQL Node 1 is active , all CRM services installed should be running and SQL Node 2 should have all CRM Services with status not running mode. When I switch to Node 2, all CRM Async services should automatically run in Node2. Can anybody please help. Thanks in advance

Many Thanks, Suresh Kumar VC

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

v22arvind 65 on at

Like (0)

Report

So you have a SQL server in cluster mode with two nodes and you want CRM async service to point to active node always?

If the CRM setup was done on the cluster name instead of a particular node, then any new async service set-up in future will automatically point to the cluster and whole active/passive handling will automatically be taken care off by sql cluster. Please elaborate if I got it wrong.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Arvind,

Thanks for your reply. Infact, we installed it on cluster name. But do I need to get Async Service be running on both nodes simultaneously that when I move the nodes, it automatically moves all the dependent process.

Best Wishes, Suresh Kumar VC

Was this reply helpful? Yes No
v22arvind 65 on at

Like (0)

Report

Ok, so you have async service installed on the db nodes itself?

Regardless of where the async service is installed, it will point to cluster only(as you have installed CRM on cluster). So, keep both instances running. When one node goes down, the other will handle.

Was this reply helpful? Yes No
Suggested answer

imayur 630 on at

Like (0)

Report

Hi,

In multiple back end server deployment load will be split automatically, So if one async service server goes down, other instance will serve. I don't think you can control this behavior, may be you can write .exe (Programatically using ServiceController in c#) to start services , when you switch.

Please let us know if you found OOB solution for this.

Was this reply helpful? Yes No