One of the best practices I talk about often is “You will fail“.
I know, not a very positive message, but it is the truth… You will fail. It is only a matter of time. Those of us who are in IT know how painful it is when there is a failure. We understand all that can go wrong. And when dealing with cloud-based solutions, the concern for an outage is even more terrifying.
Probably because it is out of our control. When there is a problem, we are at the mercy of those who operate the service. But if the cloud solution is designed properly, a disruption doesn’t necessarily mean all hope is lost.
Let’s take a look at section of the XenApp and XenDesktop Service of Citrix Cloud poster where we have StoreFront and NetScaler Gateway on-prem.
For me it is the many items going between the on-prem Cloud Connector and the cloud-hosted XenApp and XenDesktop service. If the connector cannot talk to the XenApp and XenDesktop service, what happens?
Well, until recently, you were out of luck.
But now, cloud connectors have local host cache functionality that can overcome cloud or WAN outages.
When the cloud connectors have access to the XenApp and XenDesktop Service, the remote broker provider handles the interactions between Citrix Cloud and the VDA/StoreFront/NetScaler instances. In addition, the Cloud Connector’s config sync service maintains a local cached database of the cloud-hosted XenApp and XenDesktop config.
When the Cloud Connector is unable to reach Citrix Cloud, the remote broker provider, which is responsible for handling interactions between Citrix cloud and the VDA/StoreFront/NetScaler, transfers brokering control to the high available service, which uses the locally cached database.
Even if the link between our resource location and Citrix Cloud is broken, users can still access their apps and desktops.