HPE Storage Users Group

What commands or view in the 3PAR GUI can be use to see what hosts and how much were AO'd to the SSD?

EDIT: Ran AO reports and still trying to decipher. Can someone help interpret? Looks like data was move from 0 to 1 and 1 to 0. What is the difference between USR and ADM space?

Is the space moved in MiB as shown in the charts?

Name Src Tier Dest Tier Space Space Moved
Tier2AO 0 1 usr 357504.0
Tier2AO 0 1 adm 1664.0
Tier2AO 1 0 usr 1023104.0
Tier2AO 1 0 adm 3264.0

sraomoves


DESCRIPTION
The sraomoves command shows the space that Adaptive Optimization (AO) has moved between
tiers.
S YNT AX
sraomoves [options]
AUTHORITY
Any role in the system
OPTIONS
-btsecs <secs>
Select the begin time in seconds for the report . The value can be specified as either:
• The absolute epoch time (for example 1 35 1 263600).
• The absolute time as a text string in one of the follo wing formats:
Full time string including time zone: "20 1 2- 1 0- 26 1 1 :00:00 PDT" â—¦
â—¦ Full time string excluding time zone: "20 1 2- 1 0- 26 1 1 :00:00"
â—¦ Date string: "20 1 2- 1 0- 26" or 20 1 2- 1 0- 26
â—¦ Time string: "1 1 :00:00" or 1 1 :00:00
• A negative number indicating the number of seconds before the current time . Instead of a
number representing seconds, <secs> can be specified with a suffix of m, h or d to represent
time in minutes (e.g. -30m), hours (e.g. - 1 .5h) or days (e.g. - 7d).
If it is not specified then the report begins at the earliest sample.
If it is not specified then the time at which the report begins depends on the sample category
(-hires, -hourly, -daily):
• -F or hires, the default begin time is 1 2 hours ago (-btsecs - 1 2h).
• For hourly , the default begin time is 7 days ago (-btsecs - 7d).
• For daily , the default begin time is 90 days ago (-btsecs -90d).
If begin time and sample category are not specified then the time the report begins is 1 2 hours
ago and the default sample category is hires. If -btsecs 0 is specified then the report begins at the
earliest sample.
-oneline
Show data in simplified format with one line per AOCFG.
-etsecs <secs>
sraomoves 5 27
Select the end time in seconds for the report . The value can be specified as either:
• The absolute epoch time (for example 1 35 1 263600).
• The absolute time as a text string in one of the follo wing formats:
Full time string including time zone: "20 1 2- 1 0- 26 1 1 :00:00 PDT" â—¦
â—¦ Full time string excluding time zone: "20 1 2- 1 0- 26 1 1 :00:00"
â—¦ Date string: "20 1 2- 1 0- 26" or 20 1 2- 1 0- 26
â—¦ Time string: "1 1 :00:00" or 1 1 :00:00
• A negative number indicating the number of seconds before the current time . Instead of a
number representing seconds, <secs> can be specified with a suffix of m, h or d to represent
time in minutes (e.g. -30m), hours (e.g. - 1 .5h) or days (e.g. - 7d).
If it is not specified then the report begins at the earliest sample.
–sortcol <col> [,<dir>][:<col>[,<dir>]...]
Sorts command output based on the column number (<col>). Columns are numbered from left to
right , beginning with 0. At least one column must be specified. In addition, the direction of sorting
<dir> can be specified as follo ws:
inc
Sort in increasing order (default).
dec
Sort in decreasing order .
Multiple columns can be specif ied and separated by a colon (:). Rows that have the same inf ormation
in them as earlier columns will be sorted by values in later columns.
SPECIFIERS
None
RESTRICTIONS
None
EXAMPLE S
The follo wing example shows space moved by AO beginning 2 hours (7200 seconds) ago:
cli% sraomoves -btsecs -7200
NOTE S
For this command: 1 MB = 1 04857 6 bytes.
The space reported is the space that AO has requested to be moved; the actual space moved
could be less (for example, if the move failed).

Perfect, thank you.

And usr must be actual user data and adm is some sort of meta/control data for 3PAR internal usage, tracking, etc?