This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Multi-Site Requirements
You can architect and configure XenMobile deployments that include multiple sites for high availability and disaster recovery. This article provides an overview of the high availability and disaster recovered models used in XenMobile deployments.
High Availability
- For XenMobile cluster nodes, Citrix ADC handles the load balancing. For more information, see Configure Clustering
- XenMobile Server nodes operate in an active/active configuration.
- More XenMobile Server nodes are added to a high availability cluster as capacity is required. One node can handle up to approximately 8,500 user devices (see Scalability and performance for more details).
- Citrix recommends configuring “n+1” XenMobile Servers: one server for every 8,500 user devices and one extra server for redundancy.
- Citrix recommends high availability for all Citrix ADC instances wherever possible to allow the configurations to sync with a second Citrix ADC.
- The standard Citrix ADC high availability pair operates in an active/passive configuration.
A typical high availability XenMobile deployment typically includes:
- Two Citrix ADC instances (VPX or MPX). If the Citrix ADC SDX platform is used, high availability must also be considered.
- Two or more XenMobile Servers configured with the same database settings.
Disaster Recovery
You can configure XenMobile for disaster recovery across two data centers with one active data center and one passive data center. Citrix ADC and Global Server Load Balancing (GSLB) are used to create an active/active data path so that the user experience is that of an active/active setup.
For disaster recovery, a XenMobile deployment includes:
- Two data centers - each contains one or more Citrix ADC instances, XenMobile Servers, and SQL Server databases.
- A GSLB server to direct traffic to the data centers. The GSLB server is configured for both the XenMobile enrollment URL and Citrix Gateway URL handling traffic to the site.
- When you use the Citrix ADC for XenMobile wizard to configure the Citrix Gateway, by default, the GSLB is not enabled to resolve traffic to the XenMobile enrollment server and traffic to the Citrix Gateway, en route to the MAM load-balancing server. As a result, more steps are required. For more information on preparing for and implementing these steps, see Disaster Recovery.
- Clustered SQL Servers of Always On Availability Groups.
- Latency between the XenMobile Servers and SQL Server must be less than 5 ms.
Note:
The disaster recovery methods described in this handbook provide only automated disaster recovery for the access layer. You must manually start all XenMobile Server nodes and the SQL Server database at the failover site before devices can connect the XenMobile Server.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.