Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

Scale Out File Servers for IIS .NET Data

$
0
0

Hello,

I am having a difficult time finding a direct answer online about whether or not my specific scenario warrants the use of an SOFS cluster, or just a traditional File Server cluster. 

SCENARIO:

  • Roughly 30 Windows Server 2012 R2 Standard Web servers running IIS 8.X
  • Approximately 600 websites all running ASP.NET 4.0 applications
  • Each website requires 5 different Virtual Directories. 
  • Each Website is actually a radio station, and their content is very heavy on streaming media, pictures, and dynamic live content including streaming live radio broadcasts.
  • The Cluster is connected to a SAN via 8Gbps redundant (MPIO) Fiber Channel for the source of shared storage
  • We have 3 physical hosts in the Windows cluster that will accommodate either the SOFS or the traditional File Server

So basically here's my quandary.  I've set this up a number of times, and never got it to a point where I could put any sort of load on the platform to see a difference.  I fully grasp the concepts of both, but the problem is, I see very little documentation out there regarding others using SOFS technology for IIS Virtual Directories.  I do see that there are posts stating that it's actually part of it's core function aside from Hyper-V and SQL as well. 

So, anyone out there using this in a real world scenario?  Any recommendations on whether I should or should NOT be deploying an SOFS based on the information above?  If yes, or no, then why in either direction? 

I'm really looking to put a nail in the coffin on this question.  I actually have an advisory case opened up right now too, and even the first guy I talked to couldn't answer the question.  He said he'd have to get back to me.

Any help is GREATLY appreciated!  Have a good one!


Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>