• Do not protect vCenter Server or utility VMs created by vCenter (names starting with “vCLS”).
  • Do not change a protected VM’s virtual disk configuration (provisioning, base policy, placement, etc., except of disk size). The configuration change would be ignored or may lead to unintended consequences, like stopping the protection. If it is necessary to change the virtual disk configuration, stop protection, make configuration changes, and then restart protection. An exception is that the size of virtual disks under protection can be increased.
  • Full VM clones of protected VMs can be created but are not protected automatically. While full clones are being created, data replication of the protected VMs will continue without interruption. After full cloning is complete, a cloned VM will have a JetStream DR storage policy attached, but it will be running in bypass mode. To enable protection of the cloned VM, remove the JetStream DR storage policy from the cloned VM’s disk(s) through vCenter, then add the cloned VM to a protected domain through the JetStream DR GUI.
  • Do not protect VMs with fault tolerance enabled. Start protection attempt will be rejected.
  • Protecting VMs configured with linked-clones is not supported. This is a VMware VAIO API limitation. Start protection attempt will be rejected. However, JetStream DR does not prevent creating linked clones of protected disks.
  • Moving a protected VM to a different ESXi cluster is not supported and will break protection. Protected Domains are associated with a specific ESXi cluster. Prior to migrating a protected VM from one cluster to another, stop protection on the VM. Then, after the VM has been moved to the new cluster, it can be added to a protected domain on the destination ESXi cluster.
  • Do not remove a disk from a protected VM unless the disk has been deleted. If the disk is removed from one VM and later added to another VM, it may cause protected domain failures. This behavior will be addressed in a future release.
  • Do not unregister a protected VM from the vCenter inventory. Unregistering a VM while it is protected could lead to unexpected behavior on protected and recovery sites. If possible, the suggested workaround is to remove the VM from the domain. (DRBC-7496, DRBC-7709)
  • Do not add or remove the JetStream DR storage policy manually in vCenter unless it has been recommended in the Special Events Handling section.