跳转到主内容

90 天分级无法按预期运行

Views:
2
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

适用于

  • ONTAP 9
  • FabricPool

问题

  • 卷未将冷数据分层到云层。
  • 分级策略设置为自动,最小冷却天数设置为 90。
  • 聚合已达到默认分层满度阈值(默认情况下为 50%)和容量阈值。
  • "volume show-footprint" 我们确实看到一些数据是分层的。 

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 日志表明正在进行分层:

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

  • 命令 "object-store tiering show -instance" 确认定期进行分层,没有报告错误。

::*> 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: -

  • 手动触发分层对分层数据量没有影响。 

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

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.