Skip to main content
NetApp Knowledge Base

Does Trident support ONTAP Aggregate autobalancing?

  1. Last updated
  2. Save as PDF
Views:
51
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

Astra Trident - all versions

Answer

Yes.  ONTAP's Aggregate Autobalancing is supported with Trident.
 
Application Notes:
  • Trident provisions volumes by interacting with ONTAP using the credentials and configuration provided in its backend definition. When using the ontap-nas or ontap-san drivers, you can specify one or more aggregates in the backend configuration.
  • If you specify multiple aggregates in the backend file, Trident will choose one based on available space and other policies. If you specify only one aggregate, all volumes go there. Trident itself does not move volumes between aggregates after provisioning.
  • ONTAP's Aggregate Autobalancing can move volumes between aggregates in the background to optimize space and performance. This is transparent to clients accessing the volumes via NFS/iSCSI.
  • Trident is not aware of ONTAP's aggregate autobalancing. Trident only cares about the SVM and volume names. Once a volume is provisioned, Trident tracks it by name and SVM, not by aggregate. ONTAP can move volumes between aggregates without breaking access. This is handled internally by ONTAP, and the logical path to the volume does not change. There are no known incompatibilities. Trident does not need to be aware of the aggregate location, as ONTAP handles the movement transparently.
  • You can enable aggregate autobalancing in ONTAP, and Trident will continue to function normally. Trident does not need to monitor or assign aggregates manually, and ONTAP will handle the balancing of volumes across aggregates in the background.

Additional Information

additionalInformation_text
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.