<div>
I feel that the easier way is to virtualize things. That protects from hardware failure. <br />
<br />
Next is Internet connection failure. After that is application load issues. IMO app load issues are the only good reason to mess with clusters and load balancing. <br />
<br />
What are you looking to protect against?
</div>


I feel that the easier way is to virtualize things. That protects from hardware failure.

Next is Internet connection failure. After that is application load issues. IMO app load issues are the only good reason to mess with clusters and load balancing.

What are you looking to protect against?

<div>
We have all of that resilience already. <br />
<br />
It's resilience at the database and IIS front-end that's important.
</div>


We have all of that resilience already.

It's resilience at the database and IIS front-end that's important.

<div>
I decided a while ago that the complexity of this type of setup wasn't worth any resiliancy that might get added. Frequently the single point of failure just shifts to the load balancer and doesn't disappear. I'll let someone else help from here. Sorry.
</div>


I decided a while ago that the complexity of this type of setup wasn't worth any resiliancy that might get added. Frequently the single point of failure just shifts to the load balancer and doesn't disappear. I'll let someone else help from here. Sorry.

<div>
<div class="content wysiwyg-content">
We have a website hosted on a Windows Server 2008 R2 server. We want to make the website more resilient and wondered what options there are to achieve it. The website stores data on a SQL Server.<br />
<br />
Is it a question of introducing a second server, creating an IIS 'farm', configuring SQL database mirroring for the database and then setting up WNLB?<br />
<br />
Any guidance on what's involved and steps would be appreciated.
</div>
</div>


We have a website hosted on a Windows Server 2008 R2 server. We want to make the website more resilient and wondered what options there are to achieve it. The website stores data on a SQL Server.

Is it a question of introducing a second server, creating an IIS 'farm', configuring SQL database mirroring for the database and then setting up WNLB?

Any guidance on what's involved and steps would be appreciated.

IIS Resilience

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.

Microsoft IIS Web Server

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.

Microsoft SQL Server 2008

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.