CaptainGiblets
asked on
IIS Load balancing
Hi, i have an internal website that currently runs on one windows 2012 R2 server.
I want to add some failover so i wanted to create a Load balanced solution with 2 servers.
All this is straight forward, its not external facing so i have just published an internal certificate for url Database
Currently users connect to http://server1
I Have set up an exact replica on a machine called server2 and i plan on pointing the DNS Database to the NLB IP address.
So my problem is, on my original web server there are 2 sites the front end and the back end. Due to cross site scripting the back end URL has to be the same as the URL i access the front end on just with a different port or it wont connect.
If i set up the load balance and change all urls to https://database if a person is sent to Server1 and it tries to access the back end, half the time will it try to access the back end on server2 creating extra network traffic? Or will it know to access it on its own IP.
hopefully this makes some sense! Any help is appreciated.
I want to add some failover so i wanted to create a Load balanced solution with 2 servers.
All this is straight forward, its not external facing so i have just published an internal certificate for url Database
Currently users connect to http://server1
I Have set up an exact replica on a machine called server2 and i plan on pointing the DNS Database to the NLB IP address.
So my problem is, on my original web server there are 2 sites the front end and the back end. Due to cross site scripting the back end URL has to be the same as the URL i access the front end on just with a different port or it wont connect.
If i set up the load balance and change all urls to https://database if a person is sent to Server1 and it tries to access the back end, half the time will it try to access the back end on server2 creating extra network traffic? Or will it know to access it on its own IP.
hopefully this makes some sense! Any help is appreciated.
ASKER
I read through that and it says it keeps the same client IP on the same server.
However for the back end it would be the server making the call not the client.
Would Single affinity still stop 1 server talking to the other server for information it already has locally?
However for the back end it would be the server making the call not the client.
Would Single affinity still stop 1 server talking to the other server for information it already has locally?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the help.
look to the bottom of the article
https://technet.microsoft.com/en-us/library/bb687542.aspx