XenDesktop Failover Cluster
There are many articles on the Internet devoted to the installation and initial setup of the VDI solution from Citrix - XenDesktop. But, as usually happens with such descriptions - they are superficial and do not cover numerous nuances. I decided to tell about the solution of an important nuance - my experience in implementing a failover cluster
XenDesktop.
the company decided to create its own small data center (a story about it is a matter of a separate conversation), and transfer to it the work of the entire branch network (several dozen), but it does not matter. It was necessary to build a fault-tolerant system on XenDesktop to connect> 500 users, virtual tables - windows 7.
Solutions for virtual desktops were selected from Citrix - XenDesktop. No external integrators were involved. Execution time - as usual, “should be yesterday”.
It was deployed on 6 Windows Server 2008 R2 servers (for now I’ll only talk about the logical model), namely:
2 citrix Web servers (WA-01, WA-02)
2 XenDesktop Application Servers (DDC-01, DDC-02)
1 database server (DB)
1 license server (License)
In parentheses are the names for understanding the description on the diagram.
')
Initially, the scheme was built fault-tolerant, the only weak link - the database, but it was reserved by means of MSSQL. With this approach, the failure of any link did not affect the work of XenDesktop. In this solution, no homogeneous elements (for example, Web servers) were located on the same hardware (all elements were virtualized) and were located on different hosts. Thus, maximum reliability was achieved and high availability was ensured.
Even such a scenario indicated in the figure did not stop XenDesktop and hundreds of users continued to work without downtime.
Of course, the number of elements in a cluster can be even greater, but using work on different hosts and in addition, relying on virtual server backups, the highest level of reliability was ensured.
I basically in this article on told about the internal setting - so far only theory. Hopefully, when planning your XenDesktop high availability infrastructure, a similar approach to your solution will come in handy.
XenDesktop.
Disposition:
the company decided to create its own small data center (a story about it is a matter of a separate conversation), and transfer to it the work of the entire branch network (several dozen), but it does not matter. It was necessary to build a fault-tolerant system on XenDesktop to connect> 500 users, virtual tables - windows 7.
Solutions for virtual desktops were selected from Citrix - XenDesktop. No external integrators were involved. Execution time - as usual, “should be yesterday”.
Decision:
It was deployed on 6 Windows Server 2008 R2 servers (for now I’ll only talk about the logical model), namely:
2 citrix Web servers (WA-01, WA-02)
2 XenDesktop Application Servers (DDC-01, DDC-02)
1 database server (DB)
1 license server (License)
In parentheses are the names for understanding the description on the diagram.
')
Initially, the scheme was built fault-tolerant, the only weak link - the database, but it was reserved by means of MSSQL. With this approach, the failure of any link did not affect the work of XenDesktop. In this solution, no homogeneous elements (for example, Web servers) were located on the same hardware (all elements were virtualized) and were located on different hosts. Thus, maximum reliability was achieved and high availability was ensured.
Even such a scenario indicated in the figure did not stop XenDesktop and hundreds of users continued to work without downtime.
Of course, the number of elements in a cluster can be even greater, but using work on different hosts and in addition, relying on virtual server backups, the highest level of reliability was ensured.
I basically in this article on told about the internal setting - so far only theory. Hopefully, when planning your XenDesktop high availability infrastructure, a similar approach to your solution will come in handy.
Source: https://habr.com/ru/post/159923/
All Articles