Leostream is the industry’s most widely deployed vendor-independent remote desktop connection management solution, enabling enterprises to integrate the complex array of clients, hosting platforms, guest operating systems, and display protocols required for successful VDI, hosted desktop, and application
Key benefits of load balancing
Here are a few key benefits:
- High Availability – to ensure your users are always able to log in
- Optimized performance of your connection brokers – when integrated with global and local load balancers
- Resilience and disaster recovery – supporting continued user logins in situations when a particular data centre goes down
How to load balance Leostream
Load Balancing & HA Requirements
For high availability and scalability, it is recommended that multiple Leostream Gateway servers and multiple Connection Broker servers are deployed in load balanced clusters.
Persistence (aka Server Affinity)
Source IP address based persistence is required to successfully load balance a Leostream deployment. This is true for load balancing Leostream gateway servers and for load balancing connection brokers.
Virtual Service (VIP) Requirements
To provide load balancing and HA for Leostream, the following VIP is required:
- Leostream Gateway Service
Optionally, an additional VIP may be required as follows:
- Leostream Connection Broker Service
The focus will be on the following remote protocols. Leostream is also compatible with a plethora of other different remote connection protocols. Refer to the guide for more details.
|80||TCP/HTTP||HTTP Logon to Leostream Service|
|443||TCP/HTTPS||HTTPS Logon to Leostream Service|
|3389||TCP/UDP/RDP||(Optional) Connection to RDP Hosts|
|42966||TCP/UDP/HP RGS||(Optional) ZCentral Remote Boost (Formerly HP Remote Graphics Software)|
|4172||TCP/UDP/PCoIP||(Optional) PC-over-IP Remote Display Protocol|
|50001||TCP/PCoIP||(Optional) PC-over-IP Remote Display Protocol|
|50002||TCP/PCoIP||(Optional) PC-over-IP Remote Display Protocol|
Leostream recommends the deployment of at least a pair of gateways and also (if needed) a pair of connection brokers. This makes the Leostream services highly available: if one of the gateway servers or connection brokers becomes unavailable then there is another server still online, healthy, and able to handle client connections. In this scenario, we will position the load balancer in front of the gateways and in front of the connection brokers.
Please refer to the deployment guide for other scenarios.