Skip to main content
NetApp Knowledge Base

Why does volume move copy cloud tiered data on releases 9.6 and above

Views:
503
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9.6 and above
  • FabricPool
  • CVO
  • Amazon Web Services S3 (AWS S3)

Answer

ONTAP 9.6 introduced optimized volume move where the data in cloud tier is not moved when volume move is performed, if both source and destination aggregates are attached to the same cloud tier bucket (object store).

However there are few conditions that can make the volume move to be unoptimized, where all the data in cloud tier will be copied to performance tier and then copied back to cloud tier based on the tiering policy.

FabricPool volume move will be unoptimized where;

  1. The volume was moved with-in the same aggregate to convert from NetApp Volume Encryption to NetApp Aggregate Encryption
  2. The type of encryption used in source and destination aggregate is different, or a rekey is in progress
  3. Volume move performed with generate-destination-key option
  4. Volume was a volume clone or parent of a clone
  5. For configurations using AWS S3, if the source FabricPool was created on releases earlier than ONTAP 9.5 and the destination FabricPool was created on releases ONTAP 9.5 and above, then the volume move between these FabricPools will be unoptimized.
  6. The tiering policy was changed during the volume move. Following table shows the outcome of tiering policy changes during volume move:

clipboard_efd4f96d876263081e5981ddc6426522d.png

 

 

 

******************************************************* *******************************************************