If Start Protection fails for a single VM with a large number of disks (20+) then vCenter may not reset the disk policy to the original state due to a known VMware issue.
Workaround: Apply the required disk policy manually or set to Datastore default using vCenter → VM → Edit Settings. This will ensure disks are reset to their original state.
The maximum number of virtual disks that can be protected on a single (powered on) VM is 16. This is a VMware limitation.
DO NOT make any configuration changes to protected VMs after the protected domain has failed over to the recovery site using Planned Failover (PFO) and before resuming the Continuous Failback rehydration process back to the protected site. (DRBC-6516)
The protected VM log can be throttled and might not proceed afterwards. This is a VMware issue related to IOFilter subsystem logging. Refer to the VMware recommended workaround to resume logging: The vmware.log file of a virtual machine reports >> and stops logging (2012441) [https://kb.vmware.com/s/article/2012441]. ESXi hypervisor fix is expected in version 8.0U2. (DRBC-7023)
After any kind of full recovery, the policy for the VM base folder is set 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 would be cancelled. (DRBC-6890)