Solved

W2003 Clustering Advise For Web Servers...

Posted on 2004-08-23
6
244 Views
Last Modified: 2013-11-15
Hello all.  I'm currently looking into clustering and wondering what you guys would do in my situation.

I currently have one web server that hosts 6 web sites and it has started to get enough traffic that it slows down dramatically and even stops serving (ColdFusion actually stops serving) once we hit our high peeks during the late afternoon.  We're planning on hosting up to 6 more sites on this/these servers in the future.

So I'm wondering what are we to do?  Our options are below:

-- Option 1: No Clustering --
1 Web Server - Host 3 web sites
1 Web Server - Host the other 3 sites
-----------------------------
Benefit: No need for Win 2003 Enterprise Licenses or Attached Storage
Downfall: Not fault-tolerant
Downfall: We have to carefully pick which server each site will go on
-----------------------------

-- Option 2: Clustering --
1 File Server - Host the data for each node in the cluster
1 Web Server - Share hosting responsibilities for all six sites
1 Web Server - Share hosting responsibilities for all six sites
-----------------------------
Benefit: Fault-tolerant, easy to add more nodes in the future
Downfall: Pricier, Need to buy a file server and W2003 Enterprise
-----------------------------

I guess my first questions are:  Can I reliably host 12 decent sized sites, and even more on a cluster like this?  In one way having only a few sites localized to one computer allows that computer to dedicate more memory and resources to those few sites.  On the other hand, if we can cluster and we run into processor problems again in the future we can simply add another server to the cluster to load-balance a bit more.

Thanks.  I know this is a difficult question to definitively answer, but I will do my best to accept the answers that help me in the direction we're trying to go.

Andrew
0
Comment
Question by:rebies
  • 3
  • 3
6 Comments
 
LVL 34

Expert Comment

by:Dave_Dietz
ID: 11877257
Option 2 is the best bet - hands down.  But, if I may make a suggestion - check into Windows 2003 Web Server edition for your front end machines.  You'll have to talk to an OEM about it since you can't easily buy W2K3 WSE directly, but it is designed for exactly what you're looking to do.

It will only support two CPUs per box and has a RAM limitation of 2GB (may be 4 but I believe it's 2) and there are some other limitations on what software you can install, but it is also less expensive than Enterprise Edition and it natively supports WLBS out of the box.

Buy yourself a couple blade servers with W2K3 WSE and a 2003 Standard edition as a file server and you should be good to go.  :-)

Dave Dietz
0
 
LVL 1

Author Comment

by:rebies
ID: 11877786
Dave, can you explain further why you say:  "Buy yourself a couple blade servers with W2K3 WSE and a 2003 Standard edition as a file server and you should be good to go."

Why is W2K3 Standard recommended for a file server?  Also, in the past I have stayed away from the Web Server as it does not include the Internet Connection Firewall, but is this as big of a deal that I make of it?

Andrew
0
 
LVL 34

Accepted Solution

by:
Dave_Dietz earned 500 total points
ID: 11877962
Blade servers will likely cost less than regular servers because they don't use as many components and have limited expansion capability.  Additionally they take up less room and can be installed in a higher density configuration.  Not a big deal if you're looking at two or three, but if you expand beyond that regualr server can take up wuite a bit of room compared to a stack of 1U blade servers.

Standard Edition will serve well as a file server.  Web Server Edition has a limitation on the number of inbound SMB requests so it isn't well suited to the role of a file server.  If you wanted to work with some sort of SAN device that would work as well.  As a matter of fact 2000 Server (or even NT) would work fine as a back end file server for a cluster of Load Balanced front-end blade web servers.

ICF is fine for personal machines or for machines on an Intranet, but if you are planning on making these Internet facing servers it would be best to put a decent Firewall (device or ISA server) in front of them to protect them from malicious access attempts.

                                   +-  Load Balanced web server -+      +-> back end file server(s)
Internet -> Firewall --> +-  Load Balanced web server --+----+
                                   +- (Load Balanced web server)-+      +-> back end DB server(s)

With a setup like this you have protection at the front, a scalable and fault tolerant presentation layer in the middle and easy to maintain data on the backend.

Dave Dietz
0
Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

 
LVL 1

Author Comment

by:rebies
ID: 11878524
Okay, a few more quick questions to see if I can't get closer to what I'm looking for:

1.) How do I sync IIS settings?  I've read that you should not run a Load-Balanced Cluster with a Failover cluster, so if I'm load-balancing what is the best way to synchronize settings in IIS across the servers?  (From what I'm reading, it looks like the WWW Clustering is a failover clustering only)

2.) Along the same lines, is there a way to automatically synchronize the system DSNs (ODBCs) across these servers?  I have not found anything about clustering ODBCs, so I'm wondering if this is possible.  Or maybe accomplishable with Active Directory; which happens to be another thing I am unfamiliar with.

Andrew
0
 
LVL 1

Author Comment

by:rebies
ID: 11899157
Thanks Dave for the help.
0
 
LVL 34

Expert Comment

by:Dave_Dietz
ID: 11899332
Q1) Open the Help file for IIS 6 and do a search on iiscnfg.  This should tell you all you need to know (and probably more).....

Q2) Not sure this can be done.  Application Center 2000 only supports replicating System DSNs so I imagine there is some technical difficulty in replicating USer and File DSNs or they would likely be supported as well.  Might be able to do this with some sort of registry export/import but DB (and ODBC for that matter) are not my strong points....  :-)

Dave Dietz
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Learn about cloud computing and its benefits for small business owners.
A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now