High availability overview

When deploying Horizon Unified Access Gateways, it is important to understand how this impacts our high availability requirements. This section will provide an overview of what a highly available Horizon infrastructure that must service both internal and external clients might look like.

The following diagram illustrates a Horizon infrastructure that meets the following requirements:

Internal Horizon clients use load balanced connections to Connection Servers.
Remote Horizon clients use load balanced connections to Unified Access Gateways.
Unified Access Gateways use load-balanced connections to Connection Servers.
Unified Access Gateways must be installed in a DMZ.
There must be dedicated Connection Servers for use with Unified Access Gateway appliances; these are configured with the settings outlined in this chapter.

The following diagram does not show the connections to the Horizon desktops or applications; it is only meant to illustrate the placement of load-balancing appliances, and show how true high availability might be achieved in an environment that includes multiple Horizon Unified Access Gateways. In addition, it shows that additional Connection Servers are being used for internal clients, as these servers do not require the same client connection settings as the ones used with Unified Access Gateways:

This Horizon architecture ensures that Horizon clients will be able to connect or reconnect if either of these two scenarios were to occur:

Failure of any one of the four Connection Servers shown in the diagram
Failure of any one of the Unified Access Gateways

When designing your Horizon infrastructure, you will want make all layers of it redundant, as this is the only way to ensure the high levels of availability and performance that your end users will require. If you do not have a load balancer, and are forced to pair your UAG appliances with individual Connection Servers, you will want to ensure you have at least two UAG appliances per Connection Server for redundancy purposes. If you have a load balancer, you don't need quite this many, since it can distribute client traffic among all available servers that it is balancing traffic for.

Load-balancing the Unified Access Gateways, and also their connection to your Connection Servers, ensures that your Horizon client connections will be maintained regardless of which server fails, be it a Unified Access Gateway or the Connection Server that it is paired to.

While not specifically mentioned, it is assumed that your load balancers are also redundant to ensure that the failure of any one of them will not impact Horizon client connections.

Table of Contents for High availability overview

Create new playlist

Sign In

Sign Up

Table of Contents for
High availability overview