implement the tiering policy at the end of the current monitoring cycle. See Example 1 in
“Execution mode settings and tiering policy” (page 105)
•
If Manual is set as the execution mode, you must manually perform monitoring, issue a monitor
stop, then start relocation (see Example 2, Case 1, in
“Execution mode settings and tiering
). If you change the tiering policy settings while obtaining monitoring data,
the monitoring data is used for the next tier relocation (see Example 2, Case 2, in
mode settings and tiering policy” (page 105)
). Therefore, you do not need to perform new
monitoring.
•
If a capacity shortage exists in the tier being set, a message may appear in the
View Tier
Property
window that the page allocation cannot be completed according to the tiering policy
specified for the V-VOL. Should that occur, the page allocation in the entire pool -- including
the tier that defines the tiering policy -- might not be optimized.
NOTE:
The message that page allocation cannot be completed according to the tiering
policy does not appear when these tiering policies are set:
◦
All(0)
◦
In a 2-tier configuration, Level2(2), Level3(3), or Level4(4) which is equivalent to All(0)
When a capacity shortage exists in a tier, you can revise the setting of the tiering policy or
the configuration of tiers. If the capacity of one tier is fully exhausted, the migrating pages
are assigned to the next tier according to the tiering policy.
◦
Level1(1): When tier 1 is full, the remaining pages are allocated to tier 2. If tier 2 is full,
the remaining pages are allocated to tier 3.
◦
Level3(3): When tier 2 is full, the remaining pages are allocated to tier 1. If tier 1 is full,
the remaining pages are allocated to tier 3.
◦
Level5(5): When tier 3 is full, the remaining pages are allocated to tier 2. If tier 2 is full,
the remaining pages are allocated to tier 1.
◦
Level2(2), Level4(4), and from Level6(6) to Level31(31): When the specified tier is full,
the unallocated pages are kept in the prior tier or they are allocated to the tier that has
free space.
•
If a performance shortage exists in the tier being set, pages may not be allocated in
conformance to the tiering policy specified for the V-VOL. In that case, pages are allocated
according to the performance ratio of each tier.
As shown in the following table, allocation capacity considerations are based on the tiering
policy.
Allocation capacity considerations
Tiering Policy
Tier range and I/O performance
All(0), Level2(2), or Level4(4)
Tier range
Level1(1), Level3(3), or Level5(5)
First phase: Tier range.
From Level6(6) to Level31(31)
Allocation capacities in each tier.
◦
Tier1: The setting value(%) in Tier1 Min.
◦
Tier2: The value deducted Tier1 Max(%) and Tier3 Max(%) from 100(%).
◦
Tier3: The setting value(%) in Tier3 Min.
Second phase: Tier range and I/O performance.
104 Configuring thin provisioning
Содержание XP7
Страница 229: ...Select LDEVs window Available LDEVs table Description Item LDEV identifiers LDEV ID Create Resource Groups wizard 229 ...
Страница 303: ...Pools Volume tabs Pools Volume tabs 303 ...
Страница 378: ...Add LUN Paths wizard Select LDEVs window Available LDEVs table 378 LUN Manager GUI reference ...
Страница 381: ...Select Host Groups window Available Host Groups table Add LUN Paths wizard 381 ...