Description
Type of information
Does each V-VOL
output the log
information?
Does each pool output
the log information?
Item
Performance utilization of tier 1. The
performance utilization is the current I/O
Monitoring result
No
Yes
Performance Util
Tier1 (%)
percentage based on the maximum
performance of tier 1.
Performance utilization of tier 2. The
performance utilization is the current I/O
Monitoring result
No
Yes
Performance Util
Tier2 (%)
percentage based on the maximum
performance of tier 2.
Performance utilization of tier 3. The
performance utilization is the current I/O
Monitoring result
No
Yes
Performance Util
Tier3 (%)
percentage based on the maximum
performance of tier 3.
Lower limit in a range for tier 1.
Monitoring result
Yes
No
Tier1 Low Range
Higher limit in a range for tier 2.
Monitoring result
Yes
No
Tier2 High Range
Lower limit in a range for tier 2.
Monitoring result
Yes
No
Tier2 Low Range
Higher limit in a range for tier 3.
Monitoring result
Yes
No
Tier3 High Range
Number of pages processed in an
operation to reclaim zero pages.
Tier relocation
Yes
Yes
Reclaim Zero Page
Num
Number of a tiering policy that does not
conform to the current tier configuration.
Monitoring result
No
Yes
Non Compliant
Tiering Policy
Number
A non-compliant policy prevents tier
relocation.
Notes
1.
If the log file is lfv2 (Log Format Version 2) or later, the log file information of each V-VOL appears. If the log file is lfv 1, a
hyphen appears.
2.
When deleting pool-VOLs, ex-valid monitor information are discarded, so that the tier relocation is interrupted. After completion
of the pool-VOLs deleting, the tier determination calculation performs again and completes. Processed by this way, the valid
monitor information are re-created.
Tiering policy
The tiering policy function is used to assign a specific storage tier to a specific THP V-VOL. A tiering
policy specifies subset of tiers that is available to a given set of THP V-VOLs.
Tier relocation changes the location of previously stored data. It is performed in conformance to
the tiering policy. If a THP V-VOL is initially allocated to a low-speed tier and the tiering policy is
changed to a high-speed tier, relocation is performed in the next cycle.
For example, if you set the tiering policy level on a V-VOL(THP V-VOL) to a tier with a high I/O
speed, the data is always stored on the high-speed tier when relocating tiers. When you use that
V-VOL(THP V-VOL), regardless of the actual size of the I/O load, you can always get high-speed
responses. See
“Tiering policy expansion” (page 98)
.
When you create the THP V-VOL, you can designate one of six existing tiering policies and define
up to 26 new tiering policies. See
“Tiering policy expansion” (page 98)
and
Use the
Edit LDEVs
window to change the tiering policy settings. When tier relocation occurs, the
related tiering policy set for the THP V-VOL is used to relocate data to the desired tier or tiers.
The tiering policy does not own pool capacity. Rather, pool capacity is shared among tiers. Pages
are allocated in order of priority from upper to lower tiers in a tiering policy. When you specify
a new allocation tier, pages are allocated starting from the tier that you specify.
Smart Tiers
97