Setting up HA and load balancing for Horizon servers are not that difficult. But, getting HA for the databases Horizon needs, is a different matter. One solution is to use MS SQL AlwaysOn clustering. I have set up and moved my Horizon databases to MS SQL AlwaysOn and posted the procedure’s below.
- Microsoft SQL Server – AlwaysOn SQL Cluster – Setup
- VMware Horizon – Move EventsDB to AlwaysOn Sql Cluster
- VMware Horizon – Move ComposerDB to AlwaysOn SQL Cluster
- VMware App Volumes – Migrate database to AlwaysOn Sql Cluster
PS: I’m in no sense an expert when it comes to MS SQL, and I’m 100% sure there are other easier ways to achieving the same outcome, but this is how I did it, and it works great in my lab-setup.
VMware Horizon View planning, deployment etc.
Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.
bjosoren's IT-Tech blog 
Setting up high availability (HA) and load balancing for Horizon servers may not pose significant challenges. However, ensuring high availability for the required databases presents a different set of considerations. The author suggests employing MS SQL AlwaysOn clustering as a viable solution. Having personally configured and migrated Horizon databases to MS SQL AlwaysOn, the detailed procedures are outlined below.
LikeLike