Add client software to failover cluster

Good day All;

The main objective of our effort is to have a third party program operate on a failover cluster.  The OS is Windows Server 2012 Datacenter loaded on 2 nodes. A virtual node exists along with supporting disks. This client software uses a SQL Server database.  SQL Server 2012 Enterprise is installed and operating in a failover environment.  However the client software is not failing over. If the connection to node A is lost, SQL Server fails over to node B.  But the client application does not. 

What needs to occur in order to associate the client software with the failover cluster?  This software has 6 services total installed. Some are referred to as servers - looks like to communicate between remote client computers and the database. What is the process to associate the client software with the failover?

Thank you for your help.

July 17th, 2015 4:13pm

The question is how is the client application connectiong to the database . typically they used the database server name and instance and it should be mentioned in the connection string/config file.

if this is mention, it does not matter where sql is running as long as sql is running...

so, how is the application connecting to the sql?

Free Windows Admin Tool Kit Click here and download it now
July 17th, 2015 4:38pm

Hello!

I did this once with Oracle Golden Gate on Windows (2 node WSFC) and it worked fine.

As far as I can remember, I followed the following steps:

- I installed the application in both of the servers separately.

- Add the application to the Cluster Resource Group as an Application.

- Make sure all the nodes are possible owners of the resource.

- Make sure it has these dependencies:

- The database resource,

- The disk resource that contains your application's shared files.

And start performing failover tests to see if it works for you too.

July 17th, 2015 4:50pm

What does this application does ? Does it requires to connect to SQL Server ?

Why not install it on different machine and connect SQL Server using Virtual SQL Server name which gives you advantage of not being dependent on which node SQL Server is running. 

Or you can install software on both nodes

Free Windows Admin Tool Kit Click here and download it now
July 18th, 2015 2:31am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics