January 12, 2010 – 10:38 am | No Comment

Well, yet another project makes the front page of local media!
Link to original story!

Aberdeen, South Dakota, is a great city to live in.  It is a great city to raise a family in.  Most of …

Read the full story »
PPC

Internet Marketing

Reputation Management

SEO

Social Media

Home » Virtualization

Virtualizing WFE’s, or Web Front Ends

Submitted by Nick on July 22, 2008 – 8:29 pmNo Comment

Think of a normal N-tier application running on a single Windows 2003 Small Business Server.  You likely have multiple servers/services providing support for the web application via ISA, Exchange, SQL Server, IIS, Active Directory, etc., all running on the same physical box.

Now think of the common bottlenecks in this situation: w3wp.exe (IIS App Pool worker processes) stopping, Exchange store corruption, SQL server latency, Disk I/O latency, etc.

For a web host, using virtualization to segregate these different tiers can be essential to a secure and fault tolerant infrastructure.

First, let’s examine the benefits of segregating the WFE’s (IIS) from the rest of the group.  Having a WFE on a virtual server allows you to quickly recover from most disasters/compromises, quickly scale or downsize your farm, and above all, you can now efficiently reduce the total physical resources required to serve sites/services.

By having a master image, preloaded with required 3rd part applications, components, services, and disk configurations, you can greatly reduce the amount of time it takes to produce new front end webservers.  Some may say that a disk image will give you the same benefit, but with virtualization, you’re also able to dynamically adjust network settings and RAM amounts. In addition, adding disks/SAN resources to the server is extremely simplified compared to having to manually configure and match a RAID configuration to a disk image.

Having multiple virtual front ends also enables you to more efficiently use your centralized storage. Instead of leaving wasted space on a physical server’s hard drives/array, you are now able to reduce the HDD footprint of the VM’s OS partition, and eliminate the need for replication or wasted space on unused physical disks.

Security is also enhanced when you separate the WFE from the SQL store.  Having the SQL farm outside your DMZ not only contributes to a more secure environment, it also reduces the amount of disaster recovery time required in the event if a server rebuild.

Popularity: 1% [?]

Leave a comment!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.