Attempting to immediately take a snapshot of a restored, offline VM after failback or failover may fail. This condition is transient. Workaround: Wait a period of time then retry taking a snapshot. (DRBC-6824)
Snapshots of protected VMs will fail while their respective DRVA appliance or replication log are down. (DRBC-6529)
Logical consistency-based I/O errors may appear for VMs running on a snapshot. This is a known VMware issue fixed in ESXi 7.0 u3f. For more information refer to: VMware ESXi 7.0 Update 3f Release Notes. [https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3f-release-notes.html] (DRBC-6767)
If the DRVA or replication log is not available, vMotion of an affected VM will fail with a timeout error. This condition may occur for a period of time depending upon the number of disks involved. Eventually, the VM will become responsive again on the source host. (DRBC-7046)
In contrast to previous versions, reverting to a VM snapshot with JetStream DR 4.3 does not cancel protection but restarts VM protection from scratch. Disks content is re-replicated completely after revert. In the rare situation of reverting to a quiesced snapshot that was taken using a previous version of JetStream DR 4.1.x, VM replication can become “frozen.” Data content in the cloud remains in its pre-revert state and the UI becomes stuck with background data size at 0. Workaround: Restart protection of the affected VM. (DRBC-7509)
When reverting to a snapshot prior to a disk being removed from the protected VM, automatic protection of the restored disk will not be started. Workaround: Remove the snapshots then stop and re-start protection. (DRBC-7463)
If the DRVA replication log is down or a DRVA is not accessible, a VM protected on the DRVA may become powered off while attempting Storage vMotion because of an internal timeout condition. (DRBC-7409)