HP 3PAR Operating System Software - Manual (Page 176)

2. In the Management Tree, right-click on AO Configurations.
3. From the menu list, select Create AO Configuration.
The Create AO Configuration wizard appears.
Configure AO
1. Select the name of the System on which AO will be configured.
2. Select the Domain (if any) to which the CPGs to be tiered belong.
3. Enter a Name for the AO Configuration.
4. Select a performance Mode from the list. The options are as follows:
•
Performance – Moves more data to the high-performance tier.
•
Balanced – Moves data such that performance and cost are balanced.
•
Cost – Moves more data to the low-performance, less expensive tier.
5. In the Tier CPGs group box, select at least two CPGs to tier from the lists provided. Only CPGs
in the selected domain that are not used in any other AO configuration will be displayed.
•
Tier 0 – High-performance tier. Select a high-performance frequently accessed CPG, such
as a RAID 1 SSD disk.
•
Tier 1 – Mid-performance tier. Select a medium-performing CPG, such as RAID 1 FC disk.
•
Tier 2 – Low performance tier. Select a low-performing, infrequently accessed CPG, such
as a RAID 5 NL disk.
6. Click Next to go to the Schedule AO page.
Schedule AO
1. If you wish to start or schedule the AO configuration at this time, select the Start or schedule
AO configuration checkbox. Otherwise, click Next to go to the Summary page.
2. Select Run Now to start the data optimization process (or the analysis of potential optimization),
or select Create Schedule to schedule the data optimization process (or analysis) for a later
time.
3. In the Settings groupbox, select a Max Run Time from the list. This value is the time frame
within which the system can move data regions each time the configuration executes. If the
data-movement process is projected to run longer than the specified max run time, the system
limits the amount of data to move. If the process runs longer than the specified max run time,
the system stops data movement as soon after the time limit as possible and still maintain data
integrity.
176 Managing VLUNs