IIS Resilience

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.
HypervizorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Aaron TomoskySD-WAN SimplifiedCommented:
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?
0
HypervizorAuthor Commented:
We have all of that resilience already.

It's resilience at the database and IIS front-end that's important.
0
Aaron TomoskySD-WAN SimplifiedCommented:
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.
0
ChrisCommented:
there are a few options to add resilience

Load Balancing is the way to add resilience to the front end
Easiest way is via a Windows NLB, just setup a second server, install IIS, create the NLB and copy webconfig/content over to the second box

We often use Hardware load balancers - of which we have two and they are clustered and then pointed at IIS server that are not in a window NLB because the are load balancing primarily for performance rather than resilience and hardware LB's do that better

At the SQL layer the expensive option is to have a Cluster of SQL servers but this means additional licencing and shared storage - you can do this within most hypervisors now.

The second option is SQL mirroring but this is only contingency and not automated failover. Also SQL mirroring is being depreciated in newer version of SQL so if you upgrade in the future you might not be able to support this configuration
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.