To use a group of replicated Connection Server instances across a WAN, MAN (metropolitan area network), or other non-LAN, in scenarios where a Horizon deployment needs to span data centers, you must use the Cloud Pod Architecture feature.

This feature uses standard Horizon components to provide cross-data-center administration, global and flexible user-to-desktop mapping, high-availability desktops, and disaster recovery capabilities.

A typical Cloud Pod Architecture topology consists of two or more pods, which are linked together in a pod federation. Pod federations are subject to certain limits.

Table 1. Pod Federation Limits
Object Limit
Total sessions 250,000
Pods 50
Sessions per pod 10,000
Sites 15
Connection Server instances per pod 7
Total Connection Server instances 350

The following diagram is an example of a basic Cloud Pod Architecture topology.

A diagram that represents the architecture of Linked Mode View.

In the example topology, two previously standalone pods in different data centers are joined together to form a single pod federation. An end user in this environment can connect to a Connection Server instance in the New York data center and receive a desktop or application in the London data center.

The Cloud Pod Architecture feature is not supported in an IPv6 environment.

For more information, see the Administering Cloud Pod Architecture in Horizon 7 document.