It's 2017 and I'm looking for some "best practices" guidance with IIS Web Farms across multiple VM servers. Pre-Server 2016 recommendations like

  • Distributed File System-Replication (DFS-R)
  • Application Request Routing (ARR) and Network Load Balancing (NLB)

might not make sense anymore given Server 2016, Clustered Shared Volumes (CSV). Azure IAAS platform also adds their own Load Balancer capability.

TechNet teases at SOFS as a "recommended" solution in the "Practical Applications" section, yet only one bullet point. https://technet.microsoft.com/en-us/library/hh831349(v=ws.11).aspx

"The Internet Information Services (IIS) Web server can store configuration and data for Web sites on a scale-out file share."

What's the latest "best practice", given Server 2016, for both on-premise and Azure IaaS (Not PaaS!)? Is SOFS (active-active) up to the task for IIS Web Farms?


You won't be able to deploy DFS-R because it can't replicate open files, and third-party locks like one from PeerLock are both expensive and unreliable. TL;DR: Stick with a recommended solution: SOFS.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.