Skip to main content
NetApp Knowledge Base

Does ONTAP apply efficiencies to blocks that are tiered-out to Fabricpool?

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

Applies to

  • ONTAP 9
  • Fabricpool
  • Efficiency
  • Deduplication
  • Compression
  • Compaction
  • Logical Replication Engine (LRE)

Answer

No, if a block gets tiered out before efficiency was applied in active file system (AFS), the block will remain in capacity-tier without efficiency applied.

Additional Information

  1. File or Block was written to a RW volume
  2. Inline efficiency was NOT applied
    • FAS with no inline efficiency supported
    • AFF under high write workload causing inline miss or inline efficiency disabled
    • DP volume updated from Snapmirror using classic Logical Replication Engine (LRE) without storage efficiencies over the wire
  3. Block is tracked in volume efficiency change-log to be picked up by next efficiency background job to scan/apply efficiency to it
  4. Background efficiency schedule did NOT yet trigger
  5. Configured tiering-minimum-cooling-days has passed and volume tiering scanner runs
  6. File or Block written in 1 is tiered out to capacity/cloud tier
  7. Background efficiency schedule triggers
  8. File or Block written in 1 remains in capacity without efficiencies applied
     
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.