I wonder why when we failover an eager zero provisioned VM, it does not just replicate itself, but rather changes to a lazy zero.
It was SQL VM and has 4 hard disks which are all set eager zeroed at first but changed to lazy zero.
This is Quincy from Zerto support team.
Zerto components by default creating the recovery disk in lazy zero thick provisioning type.
There is no option for changing this default behavior.
If the recovered VM in the future failover live should have disks in eager zero thick type, please kindly refer to the steps we discussed in your previous service request.
Can you share the steps?
“If the recovered VM in the future failover live should have disks in eager zero thick type, please kindly refer to the steps we discussed in your previous service request.”
Hi PS M,
The VPG has to be removed with keeping recovery disks and then recreated by using the kept disks as preseeding volumes, after the provisioning type of the disks is converted.
Before recreating the VPG, the kept recovery disks should be converted to Thick Eager Zero provisioning.
Please kindly refer to the following more detailed steps:
1. Back up the VPG’s details;
2. Remove the VPG with Keep Recovery Disks option selected;
3. Change the kept recovery disks to Thick Eager Zero provisioning by running the following command on the relevant host:
vmkfstools –eagerzero /vmfs/volumes/DatastoreName/VMName/VMName.vmdk
Note: Please use the correct path of the recovery disks.
More details can be found in the following VMware KB: https://kb.vmware.com/s/article/1035823
4. Recreate the VPG by using the converted recovery disks as preseeding volumes.
Can you tell me why I should recreate VPG?
Can’t original VPG take settings of disk type if source VM’s disk type would changed?
Thank you for your reply.
For changing the provisioning type of the recovery disk, you will have to remove the VM from the VPG, or remove the VPG itself when the VPG has only one VM or all VM in the VPGs are involved.
This is for fully updating the VPG’s settings which are relevant to the disk provisioning type.
Without readding the VM or recreating the VPG, there won’t be the preseeding process.
If you directly change the recovery datastore settings in the VPG, without removing the VPG or readding the VM, the VPG won’t be able to update the provisioning information of the disk.