Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Clustering a non-Cluster Aware Service

Status
Not open for further replies.

Ditig

IS-IT--Management
Dec 17, 2006
1
SA
Hi,
I have a customer who is interested in configuring ahot standby cluster configuration in which the backup server takes over immediately in case the primary server is down or the application crashes on the primary server. The application is not cluster aware but does listen on a specific port. The application takes requests and interacts with an SQL server in the background. Is there any way to set up "Microsoft Cluter Serverices" for this scenario? 2 servers running a certain application but only one is active. As soon as the slave / backup detects that the application has crashed on the primary server, it takes over the IP. Thanks for your help.
 
If the application in question runs as a service then yes you can cluster it.

MSCS requires SAN storage, etc. I'll assume that you have all of that setup.

Create a cluster group for the service. Assign an IP and Network name (VHOST1) to the cluster group.

Add a hard drive for the application to be installed on.
Bring these resources online on one of the nodes (we'll assume NODEA and NODEB are the physical nodes) NODEA in this case.

Install the software on NODEA using the shared drive as the destination drive. After the software is installed stop the service. Move the cluster group over to the NODEB server. Install the service in the same path on the same drive overwriting the files that are already there. (You can rename the folder if needed depending on the installers requirements.)

Now go back into the cluster administrator and setup a new resource with the type of Generic Service. Go through the wizard and add the service you just installed as a clustered resource. When you get to the dependencies screen setup the Drive, Host name, and IP Address as dependencies.

After you add the service as a resource bring the resource online. The service will now be running on NODEB. You can move the service to NODEA by moving the resource group.

Try connecting to the application. When you connect you will be connecting to the host name that you setup above (VHOST1).

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top