Skip to main content
NetApp Knowledge Base

NetApp VASA Provider: vMotion takes longer when working with VVOL datastores compared to traditional datastores

  1. Last updated
  2. Save as PDF
Views:
172
Visibility:
Public
Votes:
0
Category:
netapp-vasa-provider
Specialty:
virt
Last Updated:

Applies to

  • VASA Provider
  • VVOL
  • NFS

Issue

VM's that live on a vVol datastore take longer to vmotion from one ESXi host to another ESXi host compared to VM's that live on traditional datastores.  The following behavior is observed:

  • Migration takes 30 - 90 seconds or more
  • The more storage containers the VM spans, the longer the delay
  • While the VM is being vmotioned, the VM seems to be in a suspended state where the console is unresponsive.  
  • A vmotion for the same VM on traditional storage takes 2-4 seconds on average

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.