title: Session State Server redundancy
body: <p>We currently have an ASP.NET Web Application running on a single server. That server is about to hit the danger zone regarding CPU usage, and we want to deploy a second server.</p>
  
  <p>What would be the best way to handle Session State?</p>
  
  <p>We currently run InProc. But that's not an option with 2+ servers, as we want to exclude a single server from the WLB rotation sometimes to do maintenance work. Even though we use sticky load balancing, we would have to wait for all users to exit before we can exclude the server from the WLB rotation.</p>
  
  <p>So I was looking at this MSDN page: <a href="http://msdn.microsoft.com/en-us/library/ms178586(VS.80).aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms178586(VS.80).aspx</a></p>
  
  <p><strong>I guess my main question is</strong>: If we use the State Server mode. Can we ensure rendudancy by deploying the state server across two servers? To avoid having a single point of failure.</p>