HCX-VM size increases after HCX migration when using vSAN TRIM/UNMAP
Article ID: 314194
Updated On:
Products
VMware HCX
Issue/Introduction
The purpose of this document is to identify the situation where the VM size increases after using HCX vSphere Replication based migration workflows Bulk, RAV, or DR Protection.
In those cases, the VM size or disk utilization on the target vCenter shows a significant increase. However, when checking the file systems at the Guest OS level, there is no increase in disk size and there is NO impact to the VM
The current version of HBR vSphere Replication service used in HCX does not support the vSAN TRIM/UNMAP feature, so when the VM is enabled for replication, the entire data space is sent as a stream of zeros and stored at the target site so space on the replica disks is not reclaimed.
In those cases, the VM size or disk utilization on the target vCenter shows a significant increase. However, when checking the file systems at the Guest OS level, there is no increase in disk size and there is NO impact to the VM
The current version of HBR vSphere Replication service used in HCX does not support the vSAN TRIM/UNMAP feature, so when the VM is enabled for replication, the entire data space is sent as a stream of zeros and stored at the target site so space on the replica disks is not reclaimed.
Resolution
Perform TRIM/UNMAP operation before migrating the VM or at the target site after migration to reclaim the space.
A newer version of HBR vSphere Replication service compatible with vSAN TRIM/UNMAP will be available in future HCX releases to allow for compression, so data will be trimmed during replication.
The availability of this enhancement is TBD.
A newer version of HBR vSphere Replication service compatible with vSAN TRIM/UNMAP will be available in future HCX releases to allow for compression, so data will be trimmed during replication.
The availability of this enhancement is TBD.
Additional Information
Feedback
Yes
No
Powered by
