StoreFront 2.1 Planning

http://blog.citrix24.com/storefront-planning/

오래된 글이지만, 아래 고가용성 등, StoreFront를 구축할 때 고려해야할 사항들이 자세히 있어서 도움 될듯.

Decision: High Availability
If the server hosting StoreFront or the respective web service is unavailable, users will not be able to launch new virtual desktops, published applications or manage their subscriptions. Therefore at least two StoreFront servers should be deployed to prevent this component from becoming a single point of failure. The load balancing technique should be used to distribute users across multiple StoreFront servers. The list of available solutions includes, but is not limited to:
Citrix NetScaler – an intelligent load balancing appliance, which is capable of verifying the availability of the StoreFront service
Windows NLB – less sophisticated load balancing mechanisms, can perform very basic availability checks only (e.g. server up / down) but cannot determine the status of individual services. This could result in users being forwarded to StoreFront servers that cannot process new requests (e.g. server up but web service down).
DNS round robin – provides rudimentary load balancing across multiple servers without performing any checks on availability. If one server fails, only a portion of user requests will be affected.
Recommendation: At least two StoreFront servers should be deployed for redundancy reasons and Citrix NetScaler or another intelligent load balancing solution should be used for load balancing and fault tolerance. To simplify management of the StoreFront infrastructure, both servers should be member of the same StoreFront Server Goup.