HP 3PAR Policy Manager Software - Manual (Page 30)

4.14 Understanding the Policy Advisor Analysis Process
3PAR Policy Advisor User’s Guide
■ -cpg _name>|<pattern> - Specifies the names of CPGs to be considered for
analysis.
■ -tunepct <1-100> - Each group of Logical Disks associated with the specified CPGs is
analyzed for the number of PDs used by the LD. If this number is less than the supplied
percentage of available PDs, then tuning suggestions are generated. The default is 90%.
■ -list - Displays Tune Criteria, Tune Reasons, and Skip Reasons as a list rather than a table.
See The Policy Advisor Script on page 4.3 for more information about the script options.
The Policy Advisor performs a substantial amount of analysis of the current InServ Storage
Server configuration before making recommendations. When the Policy Advisor performs
extended processing operations, the status of the analysis is displayed to show you that the
operations are progressing.
The time required to analyze an InServ Storage Server configuration depends on the number
of CPGs, LDs, and provisioned virtual volumes in the system. On larger systems, an estimated 30
virtual volumes are analyzed per minute. For example, on a system with 1,200 physical disks, 25
CPGs, 400 LDs and 1,000 virtual volumes fully provisioned from CPGs, the analysis and
suggestion phases should complete in just over 30 minutes. Individual system times vary
depending on the activity on the InServ Storage Server during the analysis.
Virtual volumes created from a CPG inherit the characteristics of the CPG at the time the
tuning operations starts. For example, if a virtual volume was originally created as a RAID 1
volume with a setsize of 2, and the CPG was changed to use a setsize of 3, then the tuning
operation results in the virtual voluming changing to have a setsize of 3.
4.6.2.3 Virtual Volumes Created from Different Common Provisioning Groups
If a virtual volume draws space from different CPGs, then the virtual volume is not included in
the analysis. Information about virtual volumes divided between different CPGs is only
displayed when the -cpg option is used.
Virtual volumes may be split between CPGs for one of two reasons:
1 A running tuning operation was cancelled before the operation completed.
2 A running tuning operation failed before the operation completed.
In both cases, the Policy Advisor cannot tune the virtual volumes automatically because it does
not have enough information regarding which CPG the virtual volumes should be moved to.
Sample output from an InServ Storage Server with a CPG based virtual volume with a tuning
operation in progress is shown in the following example: