It's not a bug with Veeam but with VMware's often-buggy VDDK. You can either wait for the hotfix to become available (which has a downgraded VDDK 5.5) or revert to U3.
↧
It's not a bug with Veeam but with VMware's often-buggy VDDK. You can either wait for the hotfix to become available (which has a downgraded VDDK 5.5) or revert to U3.