Under some conditions, the disk type may change after recovery. Because of the datastore-specific way of determining provision type and a possible mismatch of the thin storage extent definition between the datastore and JetStream DR, a thin-provisioned disk may be restored as thick-provisioned. This corner case is only expected if a thin-provisioned disk is close to occupying all its allowed storage space. (DRBC-1267)
If a VM at the protected site has its “replication cancelled” or contains non-protected (e.g., non-persistent) disks, the following restriction applies after a planned failover operation: (DRBC-6519)
When a protected domain with any such VMs is running at the failover site after planned failover and continuous failback is running at the protected site, adding a new disk to the VM may result in protection being cancelled for the new disk. If this occurs, it is OK to restart protection for the VM at the failover site to re-synchronize the VM’s configuration at both sites.
If a datastore becomes unavailable for a VM protected in writeback mode with intent log on VMDK, it is possible for the VM to crash because of operation timeout while performing a snapshot or vMotion. (DRBC-5957)