When performing a restore with Fiber using VC in the config sometimes you will see Lazy Zero errors
The cause of this is that data remaining on the physical disk or LUN is not erased during creation, but is zeroed out at a later time during virtual machine read and write operations.
This message occurs when performing a restore of a VM to a VMware vCenter using SAN transport mode. VMware instead of zeroing a VMDK as it is created, they set a lazy zero bit on each block of the VMDK and clear it later.
To work around the performance issue, please perform a redirect restore to a ESX server instead of a vCenter.