Is block temperature persistent across volume moves?
Applies to
- ONTAP 9
- Fabricpool
- Tiering
Answer
No, block temperature is stored within aggregate metadata and will reset when a volume is moved to another aggregate.
Additional Information
- Two Fabricpool aggregates are configured:
myCluster::*> aggr object-store show
Aggregate Object Store Name Availability Mirror Type
-------------- ----------------- ------------- -----------
aggr2_fp svm-s3-DST available primary
aggr4_fp svm-s3-DST available primary
2 entries were displayed.- Volume
vol_fp_movemeis hosted on aggregateaggr2_fpwithtiering-policyset toautoandtiering-minimum-cooling-daysset to2. Data would get tiered out to the configured cloud-tier once it has not been read for at least 48 hours:
myCluster::*> vol show vol_fp_moveme -fields tiering-minimum-cooling-days, tiering-policy, aggregate
vserver volume aggregate tiering-policy tiering-minimum-cooling-days
--------- ------------- --------- -------------- ----------------------------
svm1 vol_fp_moveme aggr2_fp auto 2- Currently, all data is in
Performance Tier, nothing is tiered out tomyS3Fabricpoolyet.
myCluster::*> vol show-footprint vol_fp_moveme
Vserver : svm1
Volume : vol_fp_moveme
Feature Used Used%
-------------------------------- ---------- -----
Volume Data Footprint 8.12MB 0%
Footprint in Performance Tier 9.77MB 100%
Footprint in myS3Fabricpool 0B 0%- WAFL cold data reporting (cdr) statistics show
2001blocks with age of0 to 2 days(001days) old - expectation is it will be tiered out tomorrow:
myCluster::> set adv
Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.
Do you want to continue? {y|n}: y
myCluster::*> statistics start -sample-id mysample -object wafl_cdr_vol
Statistics collection is being started for sample-id: mysample
myCluster::*> statistics stop -sample-id mysample
Statistics collection is being stopped for sample-id: mysample
myCluster::*> statistics show -sample-id mysample -object wafl_cdr_vol -instance aggr_aggr2_fp_vol_vol_fp_moveme -counter blks_cooled_by_ranges|blks_scanned|blks_days
Object: wafl_cdr_vol
Instance: aggr_aggr2_fp_vol_vol_fp_moveme
Start-time: 3/24/2023 14:56:01
End-time: 3/24/2023 14:56:08
Elapsed-time: 7s
Scope: myCluster-01
Counter Value
---------------------- ------
blks_cooled_by_ranges -
0 to 2 days 2001
3 to 5 days 0
6 to 14 days 0
15 to 31 days 0
32 to 45 days 0
>45 days 0
blks_days -
000 0
001 2001- Volume is moved to another Fabricpool aggregate
aggr4_fp:
myCluster::*> volume move start -vserver svm1 -volume vol_fp_moveme -destination-aggregate aggr4_fp
[Job 1337] Job is queued: Move "vol_fp_moveme" in Vserver "svm1" to aggregate "aggr4_fp". Use the "volume move show -vserver svm1 -volume vol_fp_moveme" command to view the status of this operation.
myCluster::*> vol show vol_fp_moveme -fields tiering-minimum-cooling-days, tiering-policy, aggregate
vserver volume aggregate tiering-policy tiering-minimum-cooling-days
--------- ------------- --------- -------------- ----------------------------
svm1 vol_fp_moveme aggr4_fp auto 2
myCluster::*> statistics start -sample-id mysample -object wafl_cdr_vol
Statistics collection is being started for sample-id: mysample
myCluster::*> statistics stop -sample-id mysample
Statistics collection is being stopped for sample-id: mysample
myCluster::*> vol show -vserver svm1 -volume vol_fp_moveme -fields name-ordinal
vserver volume name-ordinal
--------- ------------- ------------
svm1 vol_fp_moveme 1- Block temerature is reset, it will take another 2 days minimum before data is tiered:
myCluster::*> statistics show -sample-id mysample -object wafl_cdr_vol -instance aggr_aggr4_fp_vol_vol_fp_moveme(1) -counter blks_cooled_by_ranges|blks_scanned|blks_days
Object: wafl_cdr_vol
Instance: aggr_aggr4_fp_vol_vol_fp_moveme(1)
Start-time: 3/24/2023 15:12:14
End-time: 3/24/2023 15:12:18
Elapsed-time: 4s
Scope: myCluster-01
Counter Value
---------------------- ------
blks_cooled_by_ranges -
0 to 2 days 0
3 to 5 days 0
6 to 14 days 0
15 to 31 days 0
32 to 45 days 0
>45 days 0
blks_days -
000 0
001 0