Skip to main content
NetApp Knowledge Base

SnapCenter creates snapshots on the wrong datastore volume after VMDK migration

Last Updated:

Applies to

  • NetApp Data Broker (NDB)
  • SnapCenter Plug-in for VMware vSphere (SCV) 4.3 and higher
  • SnapCenter Plug-in for SQL (SCSQL) 4.2 and higher


After migrating an SQL database or log VMDK and NFS datastore from one ONTAP storage cluster to another, although the VMDK path recognition shows the IP of the new SVM, the snapshots are created on the old one.
Note: for this to happen, the volume name on old and new SVM have to be identical, or the snapshot would simply fail on not finding the volume.


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.