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 such VMs is running at the failover site after Planned Failover and when Continuous Failback is running at protected site, adding a new disk to any such VM may result in protection being cancelled for the new disk. If this occurs, it should be 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 WB mode with intent log on VMDK, it is possible that VM would crash because of operation timeout when performing a snapshot or vMotion. (DRBC-5957)
If the protected disk is not 1K aligned, there could be problems when running the restore or CFO. The workaround is to resize such disks on primary side for CFO, or on respective representation VM for recovery. This issue will be fixed in future versions. (DRBC-8004)