If start protection fails for a single VM with a large number of disks (20+), the disk policy may not be reset to its original state by vCenter due to a known VMware issue. Workaround: Apply the required disk policy manually or reset the datastore to default settings using vCenter → VM → Edit Settings. This will ensure disks are returned to their original state.
DO NOT make any configuration changes to protected VMs with the following two conditions (DRBC-6516):
After the protected domain has been failed over to the recovery site with planned failover (PFO). And,
Before resuming the continuous failback (CFO) rehydration process back to the protected site.
The protected VM log may be throttled at times and might not proceed afterwards. This is a VMware issue related to IO Filter subsystem logging. Workaround: Refer to the VMware article: The vmware.log file of a virtual machine reports >> and stops logging (2012441) [https://kb.vmware.com/s/article/2012441]. An ESXi hypervisor fix is expected in version 8.0U2. (DRBC-7023)
After any kind of full recovery, the policy for the VM base folder will be reset to default. This will be addressed in future releases.
After protection is started, the policy applied to the protected VM disks must not be changed. To change the back-end policy assignment for specific disks please contact JetStream software.
If multiple disks with the same DDB UUID are attached to the same protected VM, the Protected VM Details window will only display one of them, and protection for all such disks will be cancelled. (DRBC-6890)
VM protection will be cancelled after a VM is unregistered from the vCenter and re-registered. The VM must either be re-protected or removed from protection. (DRBC-8499)