I’m sorry your experiencing frustrations with this. One thing you can do, is log into the VI Client (the VMware thick, or C#, client), select the VM, and open the Zerto tab (if you’ve installed the plugin) on that VM. This will show a description as to why the VM can’t be protected if that is the case. *If it can be protected, you’ll see the options to create a VPG or to see the current VPG summary.
If there isn’t information saying it cannot be protected, and you’ve met all the requirements outlined in the doc you’ve attached, you’ll want to contact support to look into this with you.
today, i’ve the same problem on ZERTO 6.5, i’ve seen no real answer here, as the suggestion it to evaluate these 3 pre-requisite which are all negative:
In a Hyper-V environment:
VMs that are part of Hyper-V Replica. This feature creates duplicates of VMs which are problematic for Zerto to track. In order to disable Hyper-V Replica for VMs you wish to protect, please right click them and select ‘Remove replication’. —> NONE.
VMs that have pass-through disks attached to them. This is similar to RDM in VC. However, Zerto does not support replication of such disks. –> NONE
Michele N.
