Skip to main content
NetApp Knowledge Base

Does SVM data mobility support migration of SVMs that contain qtrees?

Views:
416
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9.14.1 or later
  • SVM data mobility
  • vserver migrate

Answer

  • Yes, SVM Data Mobility in ONTAP 9.14.1 or later supports migration of SVMs that contain qtrees.
  • ONTAP 9.14.1 adds support for migrating SVMs containing user and group quotas or qtrees with SVM data mobility.
 
 
Note:  For migration of SVMs containing qtrees, both the source and destination of the vserver migrate command must be running ONTAP 9.14.1 or later.  Refer to prerequisites for additional considerations.

Earlier ONTAP versions and support for qtrees

  • ONTAP 9.13.1 or earlier do not offer support for migrating SVMs that contain qtrees.
  • If the vserver migrate command  is used to migrate a SVM containing qtrees, and the SVM is hosted on ONTAP 9.13.1 or earlier, the vserver migrate command will  fail:

Error: command failed: Cannot migrate Vserver <svm name> because a non-default
       qtree <qtree name> exists on thevolume <volume name>.  Migrating Vservers
       containing non-default qtrees is notsupported.  To view all non-default
       qtrees on the Vserver, run "volumeqtree show -vserver <svm name> -qtree
       !""".  To delete qtrees, run "volume qtree delete".

 

 

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.