Skip to main content
NetApp Knowledge Base

Does a volume move between two NAE Fabricpool aggregates require cloud tier re-key?

  1. Last updated
  2. Save as PDF
Views:
81
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • Fabricpool
  • NetApp Aggregate Encryption

Answer

  • Cloud tier data is not re-keyed when both, source and destination NAE aggregates being involved in the volume move, are attached to the same Fabricpool configuration, using the identical S3 bucket for cloud tier.
  • Performance tier data (including metadata, which always remains in performance tier) is re-keyed during a volume move between two Fabricpool NAE aggregates.

Additional Information

  • Due to the requirement to re-key the performance tier (meta-)data during volume move between two NAE Fabricpool aggregates, the volume move can be slower when compared against volume moves where no data re-keying is required.
  • Still, a volume move between two NAE Fabricpool Aggregates that are attached to identical Fabricpool S3 bucket is an optimized volume move and does not re-tier any cloud tier data, refer Why does volume move copy cloud tiered data on releases 9.6 and above.
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.