This post is more than 5 years old
28 Posts
0
154966
Advice High Availability in Designing vWorkspace Components
Dear all,
Would like to seek some advice with regards to designing highly available vWorkspace components. Let's assume that vWorkspace components are going to be deployed in vSphere or SCVMM managed hypervisors hence HA is in place if a host fails. In this situation, should we still require redundant vWorkspace components (n+1 virtual machines)?
On the other note, I understand that we can add a couple of vWorkspace Connection broker into vWorkspace Management Console and based on KB 99163 this would just work. I'm unsure how the traffic would flow when a request goes from a web access? As in, I would assume the connection broker info would be "defined" in the request from the web call to the connection broker. Or is this done automatically? Web access would randomly pick one of the connection broker to go to?
Thanks for any advice in advance
Regards,
Cyril
DELL-Terry L
29 Posts
1
June 21st, 2013 11:00
Hi Cyril,
Great questions. As with any layered IT architecture, you should plan HA and redundancy at all single points of failure as required by you environment or Service Level Agreements (SLA). For vWorkspace, the center of it's universe is SQL and you should plan failure and recovery accordingly. In some environments, full database backup may meet the HA requirement. In others, full SQL Clustering, Mirroring, Replication, or Always-On configurations may be required. With our broker, we advise N+1 deployment in most HA scenarios. As you move out to peripheral or enabling components, you should evaluate each component and its failure impact along with its recoverabilty to determine the adequate HA needs.
Load-balancing between multiple brokers is automatically performed by logic in the client connectors. In the case of Web Access, when you configure the Web Access site in the Management Console, it includes the broker list within the Web Acces configuration xml file. Like client connectors, the Web Access includes load-balancing logic that distributes client load across available brokers automatically.
If you have questions about specific components and their HA requirements or architecture, please add them into the discussions.
kcy43ccwc
28 Posts
0
June 23rd, 2013 22:00
Terry,
Thanks for pointing out the layered IT architecture. Guess that answers the question since HA should be applicable to individual layers of the infrastructure.
Regards,
Cyril