Basic Questions about Windows 2003 Server Clustering Concepts
Posted on 2007-04-09
Windows 2003 Server
SQL Server 2005
I'm looking for a way to provide some more reliability for two servers that I run. One is a web server, the other is a database server, both running Windows 2003 server.
These servers run an intranet web application that is access by about 50 employees. It would be quite a big problem for me if the application went down for a few hours.
So, I'm interested in server clustering. I'm hoping some can provide an articulate answer to the following questions. NOTE: I don't need to know HOW to setup a cluster. At this point I just need to make sure it can do what I need. I'm not looking for a bunch of links to vast clustering info, although a link to something that answers these basic questions would be helpful:
- If I have a web application that runs really well on a 2003 server and SQL 2005 server, do I have to do anything special to make that application support clustering? Or does the OS itself make everything work well in IIS and SQL Server?
- If I have two servers clustered together and I add a third, would that increase the scalability of the application, or does it only provide more redundancy?
- If I have two servers clustered together, and the power supply fails on one and the server crashes, does the application function on the first server without any downtime, or do I have to react somehow to make the clustered counterpart take over?
You can probably tell I'm not an expert in this concept. I'm just looking for some basic answers to make sure clustering is the right solution before I start deciding how to implement it. Thank you for your help.