90 day tiering not working as expected

Applies to

Issue

• Volumes are not tiering cold data to the cloud tier.
• The tiering policy is set to auto, and the minimum cooling days are set to 90.
• Aggregate has met the default tiering fullness threshold (50% by default) and capacity threshold. 
• From "volume show-footprint", we do see some of the data is tiered. 

vol show-footprint

      Volume : volume1

             Feature                                        Used Used%
             --------------------------------------------- ------------- -----
             Volume Data Footprint                         9.33TB 56%
                   Footprint in Performance Tier               5.53TB 59%
                   Footprint in Cloud Tier                     3.90TB 42% <=======================
             Flexible Volume Metadata                     55.4GB 0%
             Deduplication Metadata                       18.1GB 0%
                   Deduplication                               15.9GB 0%
                   Cross Volume Deduplication                  2.20GB 0%
             Delayed Frees                                109GB 1%
             File Operation Metadata                      4.00KB 0%
             Total                                        9.51TB 57%
             Footprint Data Reduction                     159GB 1%
                   Data Compaction                             159GB 1%
             Footprint Data Reduction in capacity tier    40.0GB 0%

             Effective Total Footprint                    9.32TB 56%

• EMS logs indicate that tiering is occurring:

[Node-01: scan_ca_tiering_wkr: wafl.scan.start:debug]: Starting composite aggregate tiering on volume volume1@vserver:xxxx.

[Node-01: wafl_scan_exempt: wafl.scan.done:notice]: Completed composite aggregate tiering on volume volume1@vserver:xxxx.

• The command "object-store tiering show -instance" confirms that tiering is happening regularly, with no reported errors.

::*> volume object-store tiering show -volume vol1 -instance
                             Vserver: SVM1
                              Volume: vol1
                           Node Name: vol1
                         Volume DSID: 1073744185
                      Aggregate Name: aggr2
                               State: waiting
                 Previous Run Status: completed
            Aborted Exception Status: -
          Time Scanner Last Finished: Tue Jun 21 17:33:56 2022
            Scanner Percent Complete: -
                 Scanner Current VBN: -
                    Scanner Max VBNs: -
 Time Waiting Scan will be scheduled: Wed Jun 22 17:33:55 2022 ＜＜★
                      Tiering Policy: auto
Estimated Space Needed for Promotion: -
                   Time Scan Started: -
              Cloud Retrieval Policy: default
            Elapsed Time Scanner Ran: 16181s
    Time of Last Space Related Error: -
         Scheduling class of scanner: -

• Triggering tiering manually has no effect on the amount of data tiered. 

::> set advanced
::*> volume object-store tiering trigger -vserver <svm> -volume <volume>