Skip to main content
NetApp Stage KB

Can Trident volumes be moved between aggregates in storage cluster non-disruptively?

Last Updated:


Applies to

NetApp Trident



  • Storage administrators have the ability to move volumes between aggregates and controllers in the ONTAP cluster non-disruptively to the storage consumer

         ONTAP: Move a volume

  • This operation does not affect Trident or the Kubernetes cluster, as long as the destination aggregate is one which the SVM Trident is using has access to

::>vserver show -vserver nfs_svm -fields aggr-list
vserver aggr-list
------- -----------
nfs_svm aggr1,aggr2

Add aggr3 to the SVM aggr-list:

::>vserver modify -vserver nfs_svm -aggr-list aggr1,aggr2,aggr3

  • If aggregate has been newly added to the SVM, the backend will need to be “refreshed” by re-adding it to Trident using the Trident backend update command, shown in this example:
    $ tridentctl update backend <backend-name> -f <backend.json> -n trident
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.