This post has already been read 1004 times!
My dear friend Patrick Redknap invited me to participate in the virtual conference #vRetreat to be technically updated by KEMP Technologies about loadbalancing Horizon View. Here is a closer look at 3 possible use cases to loadbalance your Horizon setup.
Frank Yue, who is a Solutions Architect at Kemp explained why you need to loadbalance your VMware Horizon Solution.
To achieve “Always On”. It’s highly recommended to load balance all Horizon deployments to provide availability, scalability, resiliency, and site redundancy.
You need to load balance the UAGs and the Connection Servers.
Use Source IP Affinity if possible. Use Multi port OR Multi VIP if Source IP Affinity is not possible.
- High Availability Automatic fault detection of the UAGs and Connection Servers.
- Scalability Add resources to increase capacity on demand
- Simplicity Manage Horizon without the need to adjust DNS entries
- Disaster Recovery Provide geographic site availability in DR or active active scenario’s.
Watch the recorded virtual vRetreat to see all 3 possible options to configure loadbalancing on kemp loadmaster.
|High Availability Architecture for Horizon View version 7||A video overview from VMware and Kemp outlining the architecture of VMware view and how to deploy in a highly available LoadMaster environment.|
|Configuring VMware View on LoadMaster||A quick video showing the steps to configure Horizon View load balancing from the LoadMaster Web UI.|
|VMware Horizon View Deployment Guide||Deployment guide to assist with configuring application delivery using VMware View|
|VMware Horizon View 7 Template||LoadMaster application template for VMware View|