Hi,
We are in the need of a cluster to make sure that we have 100% uptime, so in our windows inviroment we are looking on apache with windows 2003 setup with network load balancing.
Does anyone have any experience with this?
Do you know how to set it up? And guides, howto, faq around?
If you have anything to comment on, please do so for me ;)
-> Ebbe, Denmark
Apache on Windows 2003 with Network load balancing
2 posts
• Page 1 of 1
Re: Apache on Windows 2003 with Network load balancing
by Darwin » Fri Jan 26, 2007 9:30 am
Apache or any other application for that matter can run on Network Load Balancing (NLB).
Each server in the cluster is fully self-contained, which means it should be able to function without any other in the cluster with the exception of the database (which is not part of the NLB cluster). This means each server must be configured separately and run the Web server as well as any Web server applications that are running. If you're running a static site, all HTML files and images must be replicated across servers. If you’re using ASP or ASP.Net, those ASP pages and all associated binaries and support files must also be replicated. Source control programs like Visual SourceSafe can make this process relatively painless by allowing you to deploy updated files of a project (in Visual Studio.Net or FrontPage for example) to multiple locations simultaneously.
Since multiple redundant machines are involved in a cluster you'll want to have your data in a central location that can be accessed from all the cluster machines. It's likely that you will use a full client/server database like SQL Server in a Web farm environment, but you can also use file based data access like Visual FoxPro or Jet (Access) tables if those tables are kept in a central location accessed over a LAN connection.
It’s possible that the database can become your weakest link so if you’re after redundancy, make sure you also have a backup plan for your database. If you’re using SQL Server you might want to use Replication to create live shadows on a backup box for example.
Follow link for directions to set up load balancing
http://technet2.microsoft.com/WindowsSe ... x?mfr=true
Each server in the cluster is fully self-contained, which means it should be able to function without any other in the cluster with the exception of the database (which is not part of the NLB cluster). This means each server must be configured separately and run the Web server as well as any Web server applications that are running. If you're running a static site, all HTML files and images must be replicated across servers. If you’re using ASP or ASP.Net, those ASP pages and all associated binaries and support files must also be replicated. Source control programs like Visual SourceSafe can make this process relatively painless by allowing you to deploy updated files of a project (in Visual Studio.Net or FrontPage for example) to multiple locations simultaneously.
Since multiple redundant machines are involved in a cluster you'll want to have your data in a central location that can be accessed from all the cluster machines. It's likely that you will use a full client/server database like SQL Server in a Web farm environment, but you can also use file based data access like Visual FoxPro or Jet (Access) tables if those tables are kept in a central location accessed over a LAN connection.
It’s possible that the database can become your weakest link so if you’re after redundancy, make sure you also have a backup plan for your database. If you’re using SQL Server you might want to use Replication to create live shadows on a backup box for example.
Follow link for directions to set up load balancing
http://technet2.microsoft.com/WindowsSe ... x?mfr=true
Darwin
-
Darwin - Full Member
- Posts: 111
- Joined: Mon Oct 09, 2006 11:16 am
- Location: Bradenton, FL
2 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest