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!
Appendices
Constraints
The following section lists advisories and constraints to consider when using changed block tracking.
-
Changed block tracking is available only to customers with a Premium Edition license for Citrix Hypervisor. If a customer without a Premium Edition license attempts to use an incremental backup solution for Citrix Hypervisor that uses changed block tracking, they are prevented from enabling changed block tracking on new VDIs. However, if the customer has existing VDIs with changed block tracking enabled, they can still perform other changed block tracking actions on these VDIs.
-
Changed block tracking information is lost on storage live migration. If you attempt to migrate a VM that has VDIs with changed block tracking enabled, you are prevented from doing so. You must disable changed block tracking before storage live migration is allowed.
-
If a host or an SR crashes, Citrix Hypervisor disables changed block tracking for all VDIs on that host or SR. Before taking a VDI snapshot, we recommend that you check whether changed block tracking is enabled. If changed block tracking is disabled and this is not expected, this can indicate that a crash has occurred or that a Citrix Hypervisor user has disabled changed block tracking.
To continue using changed block tracking, you must enable changed block tracking again and create a new baseline by taking a full VDI snapshot. Subsequent changed block tracking metadata uses this snapshot as a new baseline.
The set of snapshots and changed block tracking data captured before the crash cannot be used as a baseline or comparison for any snapshots taken after the crash. However, the set of incremental backups taken before the crash can be used to create a VDI image to use to restore the VDI to a previous state.
For more information, see Incremental backup sets.
-
Citrix Hypervisor supports a maximum of 16 concurrent NBD connections.
-
Changed block tracking is not supported for VDIs stored on thin provisioned shared GFS2 block storage.
Additional Resources
The following resources provide additional information:
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.