Skip to main content
NetApp Knowledge Base

What is the expected behavior during VMotion with inline dedup/compression enabled?

Last Updated:

Applies to

  • ONTAP 9
  • VMware Storage vMotion


VMware Storage vMotion is not a zero copy operation from the Storage perspective.
During the move of the VMDK disks from a Volume to another, new blocks will be used to allocate the copy of the data, hence we will see a spike in the space usage in the aggregate.
No data is copied over the wire, the operation is Internal within ONTAP. Inline Dedupe is not keeping up during the operation, the spike in space usage and space difference of vmdk file from the Aggregate perspective is expected.

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.