Friday, February 08, 2013 10:16 PM
Need to setup an NLS url on the internal network and have read the implications of it not being available.
There is a clustered Hyper V environment. What is the best practice for making the NLS highly available?
- Edited by RessyR Friday, February 08, 2013 10:21 PM
Saturday, February 09, 2013 3:32 PM
NLS is a simple HTTPS Web site that must be reachable by any DirectAccess computer located on the network. Hyper-V clusters are not required for high availability. You have choice between NLB and HLB. Implementing a NLS in NLB is pretty simple. HLB will be more complex but will allow you to span NLS web site on multiple sites.
BenoitS - Simple by Design http://danstoncloud.com/blogs/simplebydesign/default.aspx
Tuesday, February 12, 2013 9:49 AM
Note that Windows NLB is not a HA solution, it is a load balancing solution. It will in most cases do the job for you and it is included in the OS whick is good but it is not application aware and will load balance requests to servers where the application (IIS) have failed. You can mitigate this by dedicating IIS on the NLS servers to NLS and not run any other site on that server in order to have a greater chance that IIS is up and running and responding to requests.
Hth, Anders Janson Enfo Zipper