Organizing a two-server scheme for an intranet application?

L

larin_alex2015-04-28 10:50:30

Windows Server

larin_alex, 2015-04-28 10:50:30

Hello!
I apologize in advance for the quality of the question, this is not my area, but it just so happens that I need to dive into this question a bit.
We have an intranet web application written in asp.net that works with ms sql subd. Now it is spinning in test mode, the management wants servers to be bought and a redundant system to be built. It is assumed that there will be two servers physically, one will be active, the second will be in passive mode, if the first server fails, the second will "wake up", and the first will be switched to passive mode automatically. For users, this should look transparent, and I also need the ability to switch servers manually so that I can force the server I need to be active if, for example, I need to service the second one.
It is planned to use the following software:
MS SQL server 2008
IIS
Windows server 2008/2012
Actually the question: please tell me the correct name of the scheme I am describing (or the closest one, similar in meaning to it), so that I can read information on this topic. Does microsoft have a ready-made solution for similar tasks, or will it be necessary to use a cluster scheme for the database, and manage servers (switching between active ones) somehow independently?
Thank you.

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

G

GraphiteLeader, 2015-04-28
@GraphiteLeader

The fact is that MS itself says that IIS does not cluster out of the box through Faiover Cluster, so it remains to make a web farm https://technet.microsoft.com/en-us/library/jj1293...
with NLB and instant processing failure, and MS SQL should be in Mirroring, because switching in the cluster will not be transparent to the user ..

C

Cront, 2015-04-28
@Cront

Here you need to understand what exactly you want to protect against, from the death of a server, data center, database, disks, etc. What is the maximum possible downtime? I would recommend to form a set of requirements for fault tolerance and only then start looking for solutions. Be sure to decide on the budget - any protection has its price.
In addition to application-level solutions such as Windows NLB (for IIS), virtual server-level solutions are also available.

A

athacker, 2015-04-29
@athacker

It makes sense to look towards virtualization. And yes, I will join the previous speakers - you need to clearly understand what specific failures you are trying to defend against.