The VRA on the target site, which can only perform a hot-expansion, will not be able to expand the disk. Therefore, the protected and mirror volumes will not match in size. For more information on this VMware limitation, visit: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2058287
- Edit the affected VPG
- Take note of all the settings of the relevant VM and then remove it from the VPG (keeping recovery disks)
- Use the vmfstools command, as explained by the following VMware KB to expand the problematic disk to the exact same size as the protected volume: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002019
- Re-add the VM to the VPG and set all disks to be preseeded. The VPG will go into a delta sync.
If you are planning on expanding a disk above 2TB within the scope of the affected platforms please see: https://www.zerto.com/myzerto/knowledge-base/how-to-expand-a-protected-volume-to-beyond-2tb-prevent-vpg-from-needs-configuration/