View PDF
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Managing for highly available implementations
Establishing a highly available network involves identifying critical components, creating redundancy for these components, and ensuring automatic failover to the secondary component if the active component fails. Critical components include:
- Database
- Provisioning servers
- vDisks and storage
Citrix Provisioning provides several options to consider when configuring for a highly available implementation, including:
- Database
- Offline database support, which allows Citrix Provisioning servers to use a snapshot of the database if the connection to the database is lost.
- Database mirroring.
- Citrix Provisioning servers
- Provisioning server failover. If a server becomes unavailable, another server within the site can provide active target devices with the virtual disk.
- Managing servers. You can load balance between provisioning servers to prevent overload and to allow server capacity to be used more effectively and efficiently.
- vDisks and Storage
Managing for highly available implementations
Share