Buffer Area Of A Tier - HP XP7 User Manual

Monitoring
information or
execution conditions
When an LDEV is
blocked. (Pool-VOL or
V-VOL)
When the depletion
threshold of the pool
is nearly exceeded
during relocation.
When execution mode
is Auto and the
execution cycle ends
during tier relocation.
When execution mode
is Manual and 7 days
elapse after
monitoring starts.
Notes:
1. The execution mode is Auto or the script is written in manual execution mode, information is monitored again and
tiers are relocated automatically.
2. The volume is monitored at the time of the next execution cycle.
3. All pages of the S-VOLs are not allocated, and the monitoring information of the volume is reset. After the page is
allocated to the new page, the monitoring information is collected.
4. Example: Pool-VOLs of SAS15K are added to the following configuration 1
Configuration 1 (before change): Tier 1 is SSD, Tier 2 is SAS10K, and Tier 3 is SAS7.2K.
Configuration 2 (after change): Tier 1 is SSD, Tier 2 is SAS15K, and Tier 3 is SAS10K and SAS7.2K.
5. The monitor information statuses are valid (VAL), invalid (INV), and calculating (PND). See
using RAID Manager" (page
mode, the information of the mode is discarded.
6. After completion of the pool-VOLs deletes, the monitor information status is changed from invalid (INV) to calculating
(PND). After completion of calculating, the monitor information status is changed from calculating (PND) to valid
(VAL).

Buffer area of a tier

Smart Tiers Z uses buffer percentages to reserve pages for new page assignments and allow the
tier relocation process. Areas necessary for processing these operations are distributed
corresponding to settings used by Smart Tiers Z. The following describes how processing takes
place to handle the buffer percentages.
Buffer space:The following table shows the default rates (rate to capacity of a tier) of buffer space
used for tier relocation and new page assignments, listed by drive type.
Drive type
SSD
Non-SSD
80 Configuring thin provisioning
Status of data Status of fixed
collection in progress monitoring information
used in tier relocation
Continued. No effect on the fixed
monitoring information.
The monitoring
information collected
during the previous
cycle continues to be
valid.
Continued. No effect on the fixed
monitoring information.
The monitoring
information collected
during the previous
cycle continues to be
valid.
At the end time of The monitoring
execution cycle, data information collected
monitoring stops. before monitoring
performance stops is
valid.
Suspended. The monitoring
information collected
before suspension is
valid.
85). In this case, the monitor information is invalid (INV). If monitoring is in continue
buffer area for tier relocation
2%
2%
Tier relocation
operations
Suspended.
Suspended.
Suspended.
Continued.
buffer area for new page
assignment
0%
8%
Solutions
After recovering the
faulty area, relocate tiers
1
again.
Add pool-VOLs, then
collect monitoring
information and relocate
1
tiers again.
Unnecessary. The
relocation is performed
automatically in the next
cycle.
Collect the monitoring
information again if
1
necessary.
"Execution modes when
Total
2%
10%