Citrix Local host Cache – connection leasing 2.0 or….
With Citrix XenApp / XenDesktop 7.12 Local host cache, better known as LHC, was introduced again. Of course everyone knows LHC from the 6.5 era, it was the solution to provide high availability when the database was unavailable. With the 7.x version Citrix abandoned LHC and relied completely on database high availability. Database high availability is fine but once the connection to that database is gone users are impacted.
Citrix’s solution to this was Connection leasing a solution that would keep a record of the last connection made. During times that the database was unavailable users would be connected based on the last connection. This sounds like a good solution in case of an outage but in pooled VDI environments this was un-workable as desktops could be in use already. The solution so it seemed was designed for a XenApp environment or for static pooled desktops.
Now, already in version 7.12, local host cache is introduced again. Is this connection leasing 2.0, LHC 2.0 or… I was wondering about what they created and wanted to put my thoughts on paper about it.. I think something is missing, it is a way forward but not the solution.
Read the entire article here, Citrix Local host Cache – connection leasing 2.0 or….
via Rob Beekmans.net