HP 3PAR StoreServ 7400 2-node HP 3PAR System Reporter 3.1.0 Software User& - Page 197
The recentsample Table, Table 67 ldrgmoves_1 Table
View all HP 3PAR StoreServ 7400 2-node manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 197 highlights
Table 67 ldrgmoves_1 Table (continued) Column adprovid ldid ld_name ldoffmb vvid vvspace vvoffmb src_tier dst_tier dst_cpgname move_reason Type Comment INTEGER PRIMARY KEY (AUTO_INCREMENT) A unique identifier for each adaptive optimization configuration. INTEGER NOT NULL The logical disk ID of the source LD region. VARCHAR(32) NOT NULL The LD name of the source LD region. INTEGER NOT NULL Offset in MiBs of the source LD region. INTEGER NOT NULL The VV ID for the source LD region. VARCHAR(8) NOT NULL The VV space of the source LD region. INTEGER NOT NULL Offset in MiBs in the VV space of the region. INTEGER NOT NULL Specifies the source tier. INTEGER NOT NULL Specifies the destination tier. VARCHAR(32) NOT NULL Specifies the destination CPG name. VARCHAR(32) NOT NULL The reason for the move, can be one of the following: • busy_space - Busy region moved to faster tier because of lack of space in source tier. • busiest - Busiest region moved to faster tier since it met movement criteria. • idle_space - Idle region moved to slower tier because of lack of space in source tier. • idlest - Idlest region moved to slower tier since it met movement criteria. • zero - Regions not accessed at all moved to slowest tier. status VARCHAR(64) NOT NULL The status can be one of the following • scheduled - The LD region move has been scheduled. • issued - The CLI command to execute the LD region move has been issued. • done - The LD region move has completed. • cancelled - The LD region move has been cancelled. done_tsecs INTEGER NOT NULL Time in secs when the LD region move was done. This is the Unix time and is the number of seconds since 0:00:00 Jan 1, 1970 GMT. The recentsample Table The recentsample_1 table contains a row for each sample resolution containing the time of the most recent sample for that resolution. Beginning with the 2.4.1 release System Reporter inserts data from each system into the database separately. Consequently, a given data table at a specific time may contain data from only some of the systems since the remaining systems' data may not have been inserted yet. In order to avoid reporting on such partial samples, System Reporter updates the recentsample table with the time of the most recent complete sample for each resolution. Administrative Tables 197