Disk space requirements for Hybrid Store (HTnM-Agent for RAID)
return to main contents page
return to "Management server" contents page
For Hybrid Store, each record is stored in a separate directory or file according to the summary category and time unit of each summary category. The required disk space for Hybrid Store is the total of the disk space requirements for each record type.
The following describes how to estimate disk space requirements, the number of files, and the number of directories for Hybrid Store.
Use the following formula also for estimating disk space requirements for Hybrid Store during a version upgrade installation, conversion, and backup or restore.
- Disk space requirements
The required disk space for Hybrid Store is the total of the disk space requirements for each record type.
A formula for estimating disk space requirements (X) for each record type (in bytes)
 X = Xi + Xii
If the record type is "PI" and the summary category is both "no summary" and "hour" (An estimate for backup data is excluded.)
zua0a01.gif
If a record type and summary category are other than those described above, or if backup data (for all the record types and summary categories) is to be estimated.
zua0a02.gif
n: Number of records
m: Number of summary categories
     : Numbers to the right of the decimal point of a calculation result are rounded up to the whole number. 
a: Size of the fixed part 1 of each record that collects performance data. Values differ by record and summary category. For details, see Table 1 Size of the fixed part 1 and variable part 1 of each record.
b: Size of the variable part 1 of each record that collects performance data. Values differ by record and summary category. For details, see Table 1 Size of the fixed part 1 and variable part 1 of each record.
c: Number of instances for each record that collects data (1 for a single instance record). For details, see the following tables:
  - For VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform, Hitachi Unified Storage VM, or Universal Storage Platform V/VM series:
    Table 6 Estimating number of instances for Agent for RAID records when collecting performance data by using the command device
    Table 7 Estimating number of instances for Agent for RAID records Estimating number of instances for Agent for RAID records when collecting performance data by using a TCP/IP connection
  - For Hitachi HUS100/AMS2000/AMS/WMS/SMS series:
    Table 8 Estimating number of instances for Agent for RAID records
d: Values differ by record type and summary category. For details, see Table 2 Values set to d, f, and h.
e: Size of the fixed part 2 of each record that collects performance data. Values differ by record and summary category. For details, see Table 5 Size of the fixed part 2 and variable part 2 of each record.
f: Values differ by record type and summary category. For details, see Table 2 Values set to d, f, and h.
g: Size of the variable part 2 of each record that collects performance data. Values differ by record and summary category. For details, see Table 5 Size of the fixed part 2 and variable part 2 of each record.
h: Values differ by record type and summary category. For details, see Table 2 Values set to d, f, and h.
CLST: Cluster size of the drive set to the data output destination for Hybrid Store (in bytes).
Table 1 Size of the fixed part 1 and variable part 1 of each record
Record Summary category (bytes)
No summary Hour, day, week, month, year
Fixed part 1 Variable part 1 Fixed part 1 Variable part 1
PI 136 114 136 194
PI_CBMB* 64 103 64 123
PI_CCMS* 64 103 64 123
PI_CHAC* 64 103 64 123
PI_CHDR* 64 103 64 123
PI_CHS 68 74 68 106
PI_CLCS 92 107 92 139
PI_CLMS 80 99 80 131
PI_CLMX* 88 115 88 155
PI_CLPS 108 106 108 154
PI_CPS* 60 54 60 74
PI_DBMB* 64 103 64 123
PI_DKAC* 64 103 64 123
PI_DKDR* 64 103 64 123
PI_ELDS* 120 178 120 274
PI_EVGS* 116 210 116 306
PI_HBAS* 88 252 88 300
PI_HWSP* 88 316 88 364
PI_JNLS 92 82 92 146
PI_JNLX* 220 274 220 498
PI_LDA 192 182 192 342
PI_LDE 168 190 168 334
PI_LDE1 168 190 168 334
PI_LDE2 168 190 168 334
PI_LDE3 168 190 168 334
PI_LDS 248 266 248 478
PI_LDS1 248 266 248 478
PI_LDS2 248 266 248 478
PI_LDS3 248 266 248 478
PI_LDSX* 372 322 372 754
PI_LDTC* 156 210 156 290
PI_LDU* 76 138 76 174
PI_LDUR* 140 126 140 254
PI_LSP* 276 489 276 777
PI_LTSP* 172 501 172 581
PI_LUSP* 156 421 156 549
PI_MBDR* 64 103 64 123
PI_MPCS* 68 135 68 155
PI_MPS* 68 135 68 155
PI_MPTS* 140 138 140 250
PI_PDOS 96 184 96 216
PI_PLS 116 74 116 170
PI_PLTI 64 131 64 147
PI_PRCS 100 143 100 175
PI_PTS 248 302 248 462
PI_PTSX* 128 114 128 226
PI_RGS 488 402 488 946
PI_RGSX* 368 354 368 786
PI_RGU* 60 166 60 186
PI_SCPS* 252 214 252 454
PI_SCS* 72 42 72 82
PI_VVTI 68 155 68 171
PD 76 230 - -
PD_CLPC 64 134 - -
PD_ELC 72 316 - -
PD_LDC 132 566 - -
PD_LSEC 112 466 - -
PD_PDX 52 194 - -
PD_PLC 128 340 - -
PD_PLF 68 147 - -
PD_PLR 72 186 - -
PD_PLTC 124 267 - -
PD_PLTR 76 243 - -
PD_PLTS 76 211 - -
PD_PTC 84 216 - -
PD_RGC 76 252 - -
PD_UMS 72 176 - -
PD_UMSX 72 200 - -
PD_VVC 88 152 - -
PD_VVF 72 171 - -
PD_VVTC 68 167 - -
Legend:
-: Not applicable
*: Weekly, monthly, and annual summaries are not supported.
Table 2 Values set to d, f, and h
Record type Summary category d f h RT retention period and unit
PI No summary
zua0a06.gif
zua0a07.gif
zua0a08.gif
Retention period (unit: hours)
Hour RT + 2 744
zua0a09.gif
Retention period (unit: hours)
Day RT + 2 - - Retention period (unit: days)
Week RT + 2 - - Retention period (unit: weeks)
Month RT + 2 - - Retention period (unit: months)
Year zua0a10.gif
The smaller value of
    and RT + 2
- - Retention period (unit: years)
PD No summary
zua0a06.gif
- - Retention period (unit: hours)
Legend:
AP: The number of scheduled operation years for Hybrid Store.
CI:
For records collected by using a command device or PD_PDX records
Setting value (in seconds) for the collection interval of performance data.
For records collected by using a TCP/IP connection
Sampling interval (in seconds) for the data that was set by Performance Monitor.
RT: The setting value for the retention period for historical data. For details, see Table 3 Retention period for the records of the PI record type (default value) and Table 4 Retention period for the records of the PD record type (default value).
Table 3 Retention period for the records of the PI record type (default value)
Data type Retention period
raw 48 hours
Hourly 216 hours
Daily 378 days
Weekly 54 weeks
Monthly 12 months
Yearly 1,000 years
Table 4 Retention period for the records of the PD record type (default value)
Record name (Record ID) Retention period (unit: hours)
CLPR Configuration(PD_CLPC) 168
External LDEV Configuration(PD_ELC) 168
Logical Device Configuration(PD_LDC) 168
LUSE Configuration(PD_LSEC) 168
Pool Configuration(PD_PLC) 8784
Pool Frequency Distribution(PD_PLF) 168
Pool Page Relocation(PD_PLR) 744
Pool Tier Page Relocation(PD_PLTR) 744
Pool Tier Type Configuration(PD_PLTC) 744
Pool Tier Type Operation Status(PD_PLTS) 744
Port Configuration(PD_PTC) 168
RAID Group Configuration(PD_RGC) 168
Storage Detail(PD) 168
Storage Detail Extra (PD_PDX) 168
Utilization Per MP Blade Extra (PD_UMSX) 168
Utilization Per MP Blade Summary(PD_UMS) 168
V-VOL Frequency Distribution(PD_VVF) 168
V-VOL Tier Type Configuration(PD_VVTC) 744
Virtual Volume Configuration(PD_VVC) 744
Note:
For the following records, performance data is collected by using TCP/IP connection, and data in the timeline format cannot be collected. Therefore, the value is always 0.
Target records:
PI_CBMB record, PI_CCMS record, PI_CHAC record, PI_CHDR record, PI_CLMX record, 
PI_CPS record, PI_DBMB record, PI_DKAC record, PI_DKDR record, PI_ELDS record,
 PI_EVGS record, PI_HBAS record, PI_HWSP record, PI_JNLX record, PI_LDSX record,
 PI_LDTC record, PI_LDU record, PI_LDUR record, PI_LSP record, PI_LTSP record, 
PI_LUSP record, PI_MBDR record, PI_MPCS record, PI_MPS record, PI_MPTS record,
 PI_PTSX record, PI_RGSX record, PI_RGU record, PI_SCPS record, PI_SCS record, PD_PDX record, PD_UMSX record.
Table 5 Size of the fixed part 2 and variable part 2 of each record
Record Summary category (bytes)
No summary Hour
Fixed part 2 Variable part 2 Fixed part 2 Variable part 2
PI 122 120 122 200
PI_CHS 70 64 70 96
PI_CLCS 95 96 95 128
PI_CLMS 91 80 91 112
PI_CLPS 102 104 102 152
PI_JNLS 86 80 86 144
PI_LDA 178 188 178 348
PI_LDE 170 180 170 324
PI_LDE1 170 180 170 324
PI_LDE2 170 180 170 324
PI_LDE3 170 180 170 324
PI_LDS 250 256 250 468
PI_LDS1 250 256 250 468
PI_LDS2 250 256 250 468
PI_LDS3 250 256 250 468
PI_PDOS 108 164 108 196
PI_PLS 110 72 110 168
PI_PLTI 91 96 91 112
PI_PRCS 119 116 119 148
PI_PTS 242 300 242 460
PI_RGS 538 344 538 888
PI_VVTI 103 112 103 128
- Number of files
The formula for estimating the number of files (x) to be created by Hybrid Store is as follows:
 X = Xi + Xii
If a record type is "PI" and the summary category is both "no summary" and "hour" (An estimate for backup data is excluded.)
zua0a03.gif
If a record type and summary category are other than those described above, or if backup data (for all the record types and summary categories) is to be estimated
zua0a04.gif
- Number of directories
The formula for estimating the number of directories (x) to be created by Hybrid Store is as follows:
zua0a05.gif
Round off the numbers to the right of the decimal point of a calculation result in     to the nearest whole number.
min(): The function that returns the smaller value of the numbers in ()
RcI: Number of collected records for PI record type
     
RcD: Number of collected records for PD record type
RcI: Number of records collected by the PI record type record
RcD: Number of records collected by the PD record type record
A1r: The setting value of the retention period for each record without a summary of the PD record type (unit: hours)
A2r: The setting value of the retention period for the hourly record for each record of the PI record type (unit: hours)
A3r: The setting value of the retention period for the daily record for each record of the PI record type (unit: days)
A4r: The setting value of the retention period for the weekly record for each record of the PI record type (unit: weeks)
A5r: The setting value of the retention period for the monthly record for each record of the PI record type (unit: months)
Ir: Number of instances for each record that collects data (1 for a single instance record)
Br: The setting value of the retention period for each record of the PD record type (unit: hours)
-Number of files to be opened by uning Manager - Agent REST Application Service
Number of files to be opened by uning Manager - Agent RESTApplication Service: max 20 files
Note that, if other Agent instances that are managed by using Hybrid Store exist on the same host, the total number of files for all Agents must not exceed 20.
Method for estimating number of instances (by using the command device)
Table 6 Estimating number of instances for Agent for RAID records when collecting performance data by using the command device
           (VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform, Hitachi Unified Storage VM, and Universal Storage Platform V/VM series)
Record name (Record ID) Method for estimating number of instances
Channel Adaptor Summary Record (PI_CHS) Number of CHAs in the storage system
CLPR Configuration (PD_CLPC) The number of CLPRs that exist in the storage system.
CLPR Per Controller Summary(PI_CLCS) N/A
CLPR Per MP Blade Summary Record (PI_CLMS) The number of instances is calculated as follows:

For Hitachi Virtual Storage Platform, VSP G1000, G1500 or VSP F1500: (number-of-MP-blades-in-the-storage-system) x (number-of-CLPRs-in-the-storage-system).

For Hitachi Unified Storage VM or VSP Gx00 models, VSP Fx00 models : (number-of-MP-units-in-the-storage-system) x (number-of-CLPRs-in-the-storage-system).

Note:
If the monitoring target is not a  VSP Gx00 models, VSP Fx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series storage system, the number of instances is 0.
CLPR Summary (PI_CLPS) The number of CLPRs that exist in the storage system.
External LDEV Configuration(PD_ELC)1 Among externally connected LDEVs that exist in the storage system, the number (for each LUN) of externally connected LDEVs to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of externally connected LDEVs will be added: the number of externally connected LDEVs to which emulation types for open systems have been set and LU paths have not been assigned, and the number of externally connected LDEVs to which emulation types for mainframes have been set.
Journal Group Summary Record(PI_JNLS) Number of journal groups in the storage system
LDEV Summary - Extended(PI_LDE)1 Among logical devices that exist in the storage system, the number (for each LUN) of logical devices to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices to which emulation types for open systems have been set and LU paths have not been assigned, and the number of logical devices to which emulation types for mainframes have been set.

Note: The logical devices subject to be counted are only hose whose logical device number is in the range from 00:00 to 3F:FF (for models that support logical DKC numbers, the eange is from 00:00:00 to 00:3F:FF).
LDEV Summary 1 - Extended(PI_LDE1)1 Among logical devices that exist in the storage system, the number (for each LUN) of logical devices to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices to which emulation types for open systems have been set and LU paths have not been assigned, and the number of logical devices to which emulation types for mainframes have been set.

Note:
- The logical devices that are subject to be counted are only those whose logical device number is in the range from 00:40:00 to 00:7F:FF.
LDEV Summary 2 - Extended(PI_LDE2)1 Among logical devices that exist in the storage system, the number (for each LUN) of logical devices to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices to which emulation types for open systems have been set and LU paths have not been assigned, and the number of logical devices to which emulation types for mainframes have been set.

Note:
- The logical devices that are subject to be counted are only those whose logical device number is in the range from 00:80:00 to 00:BF:FF.
LDEV Summary 3 - Extended(PI_LDE3)1 Among logical devices that exist in the storage system, the number (for each LUN) of logical devices to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices to which emulation types for open systems have been set and LU paths have not been assigned, and the number of logical devices to which emulation types for mainframes have been set.

Note:
- The logical devices that are subject to be counted are only those whose logical device number is in the range from 00:C0:00 to 00:FE:FF.
Logical Device Aggregation(PI_LDA) Always 1.
Logical Device Configuration(PD_LDC)1 Among logical devices that exist in the storage system, the number (for each LUN) of logical devices to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices to which emulation types for open systems have been set and LU paths have not been assigned, and the number of logical devices to which emulation types for mainframes have been set.
Logical Device Summary(PI_LDS)1 Among logical devices that exist in the storage system, the number (for each LUN) of logical devices to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices to which emulation types for open systems have been set and LU paths have not been assigned, and the number of logical devices to which emulation types for mainframes have been set.

Note: The logical devices subject to be counted are only those whose logical device number is in the range from 00:00 to 3F:FF (for models that support logical DKC numbers, the range is from 00:00:00 to 00:3F:FF).
Logical Device Summary 1(PI_LDS1)1 Among logical devices that exist in the storage system, the number (for each LUN) of logical devices to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices to which emulation types for open systems have been set and LU paths have not been assigned, and the number of logical devices to which emulation types for mainframes have been set.

Note:
- The logical devices that are subject to be counted are only those whose logical device number is in the range from 00:40:00 to 00:7F:FF.
Logical Device Summary 2(PI_LDS2)1 Among logical devices that exist in the storage system, the number (for each LUN) of logical devices to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices to which emulation types for open systems have been set and LU paths have not been assigned, and the number of logical devices to which emulation types for mainframes have been set.

Note:
- The logical devices that are subject to be counted are only those whose logical device number is in the range from 00:80:00 to 00:BF:FF.
Logical Device Summary 3(PI_LDS3)1 Among logical devices that exist in the storage system, the number (for each LUN) of logical devices to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices to which emulation types for open systems have been set and LU paths have not been assigned, and the number of logical devices to which emulation types for mainframes have been set.

Note:
- The logical devices that are subject to be counted are only those whose logical device number is in the range from 00:C0:00 to 00:FE:FF.
LUSE Configuration (PD_LSEC)1 Among logical devices that exist in the storage system, the number of logical devices that make up the LUSE to which LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of logical devices will be added: the number of logical devices that make up the LUSE and LU paths have not been assigned to.
Physical Device Operation
Status (PI_PDOS)
N/A
Pool Configuration (PD_PLC) The total number of Dynamic Provisioning and Dynamic Tiering pools that exist in the storage system
Pool Frequency Distribution Record (PD_PLF) (Number-of-Dynamic-Provisioning-pools-in-the-storage-system-that-perform-tier-management) x (number-of-partitions) (max. 126)

Note:
If the monitoring target is not a VSP Gx00 models, VSP Fx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series storage system, the number of instances is 0.

Pool Page Relocation(PD_PLR) Number of Dynamic Provisioning pools that perform tier management in the storage system.

Note: The instance count is 0 for monitoring of anything other than VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform or Hitachi Unified Storage VM is monitored.
Pool Summary (PI_PLS) The number of pools of Dynamic Provisioning that exists in the storage system
Pool Tier Page Relocation(PD_PLTR) Number of Tier that make up Dynamic Provisioning pools that perform tier management in the storage system.

Note: The instance count is 0 for monitoring of anything other than VSP Gx00 models, VSP Fx00 models,VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform or Hitachi Unified Storage VM is monitored.
Pool Tier Type Configuration(PD_PLTC) Number of Tier that make up Dynamic Provisioning pools that perform tier management in the storage system.

Note: The number of instances is 0 when monitoring instances other than VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform or Hitachi Unified Storage VM.
Pool Tier Type I/O Information(PI_PLTI) (The total number of tiers that make up all Dynamic Provisioning pools that perform tier management in the storage system) + (The number of Dynamic Provisioning pool that perform tier management)

Note: The number of instances is 0 when monitoring instances other than VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform or Hitachi Unified Storage VM.
Pool Tier Type Operation Status(PD_PLTS) Number of Tier that make up Dynamic Provisioning pools that perform tier management in the storage system.

Note: The number of instances is 0 when monitoring instances other than VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform or Hitachi Unified Storage VM.
Port Configuration (PD_PTC) The number of ports that exist in the storage system.
Port Summary (PI_PTS) The number of ports that exist in the storage system.
Processor Summary (PI_PRCS) You can calculate the number of channel processors and disk
processors in a storage system as follows:
For VSP G1000, G1500, VSP F1500 storage systems:
Number of processors in the storage system (number of MPBs x 8) + (number of MPBs)
For Hitachi VSP storage systems:
Number of processors in the storage system (number of MPBs x 4) + (number of MPBs)
For HUS VM storage systems:
Number of processors in the storage system (number of MPUs x 4) + (number of MPUs)
For VSP Gx00 models and VSP Fx00 models:
(number-of-MPUs x number-of-processors#) + (number-of-MPUs)
#number-of-processors is as follows:
-VSP G200 or VSP F200: 2
-VSP G400, G600 or VSP F400, F600: 4
-VSP G800 or VSP F800: 8
RAID Group Configuration(PD_RGC) Among parity groups that exist in the storage system, the number of parity groups to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of parity groups will be added: the number of parity groups to which emulation types for open systems have been set and LU paths have not been assigned, and the number of parity groups to which emulation types for mainframes have been set.
The number of external volume groups and virtual volume groups is not included.
RAID Group Summary (PI_RGS) Among parity groups that exist in the storage system, the number of parity groups to which emulation types for open systems have been set and LU paths have been assigned.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, the following number of parity groups will be added: the number of parity groups to which emulation types for open systems have been set and LU paths have not been assigned, and the number of parity groups to which emulation types for mainframes have been set.
The number of external volume groups and virtual volume groups is not included.
Storage Detail (PD) Always 1.
Storage Detail Extra (PD_PDX) Always 1.
Storage Summary (PI) Always 1.
V-VOL Frequency Distribution Record (PD_VVF)  (Number-of-Dynamic-Provisioning-V-VOLs-in-the-storage-system-that-perform-tier-management) x (number-of-partitions) (max. 126)#

#:
This is the number of Dynamic Provisioning V-VOLs (in the storage system) that perform tier management and to which LU paths are assigned. If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, calculate the sum of the following values: 1) the number of Dynamic Provisioning V-VOLs that perform tier management and for which the emulation type for open systems is specified and to which no LU paths are assigned, and 2) the number of Dynamic Provisioning V-VOLs that perform tier management and for which the emulation type for mainframes is specified.

Note:
If the monitoring target is not a VSP Gx00 models, VSP Fx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series storage system, the number of instances is 0.
V-VOL Tier Type Configuration(PD_VVTC)1 The following formula is use to calculate the number of instances for a Dynamic Provisioning pool that perform tier management in the storage system:
The number of tiers that make up a Dynamic Provisioning pool that perform tier management X the number of V-VOLs that belong to the Dynamic Provisioning pool#.
The total number of instances for a Dynamic Provisioning pool that perform tier management in the storage system will be the number of instances for this record.

#:
Of the V-VOLs for Dynamic Provisioning pool that perform tier management in the storage system, the number of V-VOLs to which LU paths are assigned. If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, add the number of V-VOLs for Dynamic Provisioning pool that perform tier management to which emulation types for open systems have been set and LU paths have not been assigned, and the number of V-Vols for Dynamic Provisioning pool that perform tier management to which emulation types for mainframes have been set.

Note:
The number of instances is 0 if anything other than VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform or Hitachi Unified Storage VM is monitored.
V-VOL Tier Type I/O Information(PI_VVTI) The following formula is use to calculate the number of instances for a Dynamic Provisioning pool that perform tier management in the storage system:
(The number of tiers that make up a Dynamic Provisioning pool that perform tier management) x (the number of V-VOLs that belong to the Dynamic Provisioning pool) (see notes below).
The total number of instances for a Dynamic Provisioning pool that perform tier management in the storage system will be the number of instances for this record.

Note:
- Of the V-VOLs for Dynamic Provisioning pool that perform tier management in the storage system, the number of V-VOLs to which LU paths are assigned.
- If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, add the number of V-VOLs for Dynamic Provisioning pool that perform tier management to which emulation types for open systems have been set and LU paths have not been assigned, and the number of V-Vols for Dynamic Provisioning pool that perform tier management to which emulation types for mainframes have been set.
- The number of instances is 0 if anything other than VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform or Hitachi Unified Storage VM is monitored.
Utilization Per MP Blade Summary Record(PD_UMS) For a VSP G1000, G1500, VSP F1500 storage system:
(number-of-processors-in-the storage-system) x 20.
where (number-of-processors-in-the storage-system) = (number-of-MP-Blades) x 8.
For a Virtual Storage Platform series storage system:
(number-of-processors-in-the storage-system) x 20.
where (number-of-processors-in-the storage-system) = (number-of-MP-Blades) x 4.
For a HUS VM system:
(number-of-processors-in-the storage-system) x 20.
where (number-of-processors-in-the storage-system) = (number-of-MPUs) x 4.
For a VSP Gx00 models and VSP Fx00 models system:
(number-of-MPUs x number-of-processors) x 20
where number-of-processors is as follows:
-VSP G200 or VSP F200: 2
-VSP G400, G600 or VSP F400, F600: 4
-VSP G800 or VSP F800: 8

Note:
If the monitoring target is not a VSP Gx00 models, VSP Fx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series storage system, the number of instances is 0.
Virtual Volume Configuration(PD_VVC)1 The number of Dynamic Provisioning and Dynamic Tiering V-VOLs that exist in the storage system and that are assigned an LU path.
If Y or y was specified for Unassigned Open Volume Monitoring and Mainframe Volume Monitoring when the instance environment was created, add the number of Dynamic Provisioning and Dynamic Tiering V-VOLs that are not assigned an LU path.
Note:
    1. If the logical device definition file ldev_filter.ini is used, the number of instances for this record is the
        number of logical devices that satisfy the following two conditions:
        - Logical devices whose total number was calculated using the method described in Table 6 Defaults for
          retention period and number of records for PI record type
        -  Logical devices defined in the logical device definition file
Method for estimating number of instances (by using a TCP/IP connection)
Note: For Universal Storage Platform V/VM series, performance data cannot be collected by using a TCP/IP connection. For this reason, the number of instances for each record in the following table is 0.
Table 7 Estimating number of instances for Agent for RAID records when collecting performance data by using a TCP/IP connection
           (VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, VSP F1500, Hitachi Virtual Storage Platform, and Hitachi Unified Storage VM)
Record name (Record ID) Method for estimating number of instances
Between Cache Switch and Cache Memory Summary  (PI_CCMS) Total number of the following values for each controller chassis:
- If the monitored storage system is a member of the VSP G1000, G1500, VSP F1500: Number of caches
- If the monitored storage system is a member of the Virtual Storage Platform series: (number-of-PCI-Express-switches) x (number-of-caches)

Note:
- If the monitoring target is not a VSP G1000, G1500, VSP F1500 or Virtual Storage Platform series storage system, the number of instances is 0.
Between CHA and Cache Switch Summary  (PI_CHAC) Total number of the following values for each controller chassis:
- If the monitored storage system is a member of the VSP G1000, G1500, VSP F1500:  (number-of-channel-adapters) x (number-of-caches)
- If the monitored storage system is a member of the Virtual Storage Platform series: (number-of-channel-adapters) x (number-of-PCI-Express-switches)

Note:
- If the monitoring target is not a VSP G1000, G1500, VSP F1500 or Virtual Storage Platform series storage system, the number of instances is 0.
Between CHB and Main Blade Summary  (PI_CBMB) Number of channel blades in the storage system

Note:

- If the monitoring target is not a HUS VM storage system, the number of instances is 0.
Between DKA and Cache Switch Summary  (PI_DKAC) Total number of the following values for each controller chassis:
- If the monitored storage system is a member of the VSP G1000, G1500, VSP F1500:  (number-of-disk-adapters-in-the-storage-system) x (number-of-caches)
- If the monitored storage system is a member of the Virtual Storage Platform series : (number-of-disk-adapters-in-the-storage-system) x (number-of-PCI-Express-switches)

Note:
- If the monitoring target is not a VSP G1000, G1500, VSP F1500 or Virtual Storage Platform series storage system, the number of instances is 0.
Between DKB and Main Blade Summary  (PI_DBMB) Number of disk blades in the storage system

Note:
- If the monitoring target is not a HUS VM storage system, the number of instances is 0.
Between MP Blade and Cache Switch Summary  (PI_MPCS) Total number of the following values for each controller chassis:

- If the monitored storage system is a member of the VSP G1000, G1500, VSP F1500:  (number-of-MP-blades) x (number-of-caches)
- If the monitored storage system is a member of the Virtual Storage Platform series: (number-of-MP-blades) x (number-of-PCI-Express-switches)

Note:
- If the monitoring target is not a VSP G1000, G1500, VSP F1500 or Virtual Storage Platform series storage system, the number of instances is 0.
Cache Path Summary  (PI_CPS) Number of main blades in the storage system

Note:
- If the monitoring target is not a HUS VM storage system, the number of instances is 0.
CHA DRR Summary  (PI_CHDR) The number of instances is calculated as follows:
(number-of-channel-adapters-in-the-storage-system) x (number-of-data-recovery-reconfiguration-circuits-in-the-storage-system)

Where the number of data recovery reconfiguration circuit varies depending on the storage system:
- If the monitored storage system is a member of the VSP G1000, G1500, VSP F1500: 2
- If the monitored storage system is a member of the Virtual Storage Platform series: 2

Note:
- If the monitoring target is not a VSP G1000, G1500, VSP F1500 or Virtual Storage Platform series storage system, the number of instances is 0.
CLPR Per MP Blade Summary Extra  (PI_CLMX) If the monitored storage system is VSP Gx00 models, VSP Fx00 models, or HUS VM: (number-of-MP-units-in-the-storage-system) x (number-of-CLPRs-in-the-storage-system).

If the monitored storage system is a member of the VSP G1000, G1500, VSP F1500 or the Virtual Storage Platform series: (number-of-MP-blades-in-the-storage-system) x (number-of-CLPRs-in-the-storage-system).
DKA DRR Summary  (PI_DKDR) The number of instances is calculated as follows:
(number-of-disk-adapters-in-the-storage-system) x (number-of-data-recovery-reconfiguration-circuits-in-the-storage-system)

Where the number of data recovery reconfiguration circuit varies depending on the storage system:

- If the monitored storage system is a member of the VSP G1000, G1500, VSP F1500: 2
- If the monitored storage system is a member of the Virtual Storage Platform series: 4

Note:
-
If the monitoring target is not a VSP G1000, G1500, VSP F1500 or Virtual Storage Platform series storage system, the number of instances is 0.
External LDEV Summary  (PI_ELDS) Number of externally connected logical devices in the storage system
External Volume Group Summary  (PI_EVGS) Number of external volume groups in the storage system
HBA Summary  (PI_HBAS) Number of HBAs connected to the storage system
HBA WWN Summary by Port  (PI_HWSP) Number of HBAs connected to the storage system
If one HBA is connected to multiple ports of the storage system, the number of instances is the number of ports to which the HBA is connected.
Journal Group Summary Extra  (PI_JNLX) Number of journal groups in the storage system
LDEV Summary Extra  (PI_LDSX) Number of logical devices in the storage system
LDEV TC Summary  (PI_LDTC) Number of logical devices in the storage system
LDEV UR Summary  (PI_LDUR) Number of logical devices in the storage system
LDEV Utilization  (PI_LDU) Number of internal volumes in the storage system
LU Summary By Port  (PI_LSP) Number of LU paths
A maximum of 1,000 instances by default. If port names are specified in the properties file for specifying ports   (lu_port_filter.ini), the number of instances is the number of logical devices connected to the ports specified in the properties file.
LU TC Summary By Port  (PI_LTSP) Number of LU paths
A maximum of 1,000 instances by default. If port names are specified in the properties file for specifying ports   (lu_port_filter.ini), the number of instances is the number of logical devices connected to the port specified in the properties file.
LU UR Summary By Port  (PI_LUSP) Number of LU paths
A maximum of 1,000 instances by default. If port names are specified in the properties file for specifying ports   (lu_port_filter.ini), the number of instances is the number of logical devices connected to the port specified in the properties file.
Main Blade DRR Summary  (PI_MBDR) (number-of-main-blades-in-the-storage-system) x (number-of-data-recovery-reconfiguration-circuits-in-the-storage-system)
The number of data recovery reconfiguration circuits varies depending on the model as follows:

If the monitored storage system is HUS VM: 4

Note:
- If the monitoring target is not a HUS VM storage system, the number of instances is 0.
Mainframe Port Summary  (PI_MPTS) Number of mainframe ports in the storage system

Note:
- If the monitoring target is not a VSP G1000, G1500, VSP F1500 storage system, the number of instances is 0.
MP Summary  (PI_MPS) Number of MPs in the storage system
Port Summary Extra  (PI_PTSX) Number of ports in the storage system
RAID Group Summary Extra  (PI_RGSX) Number of parity groups, external volume groups, and virtual volume groups in the storage system
RAID Group Utilization  (PI_RGU) Number of parity groups in the storage system
Storage Cache Summary  (PI_SCS) Always 1.
Storage Copy Summary  (PI_SCPS) Always 1.
Utilization Per MP Blade Extra  (PD_UMSX) If the monitored storage system is HUS VM, the number of instances is the number of processors in the storage system (number-of-MP-units) x (4 processors) x 100
If the monitored storage system is a member of the Virtual Storage Platform series, the number of instances is estimated by multiplying the number of processors in the storage system   (number-of-MP-units) x (4 processors) x 100.
If the monitored storage system is a member of the VSP G1000, G1500, VSP F1500, the number of instances is estimated by multiplying the number of processors in the storage system   (number-of-MP-units) x (8 processors) x 100.

Note:
- If the monitoring target is not a HUS VM, VSP G1000, G1500, VSP F1500 or Virtual Storage Platform series storage system, the number of instances is 0.
Table 8 Estimating number of instances for Agent for RAID records (Hitachi HUS100/AMS2000/AMS/WMS/SMS series)
Record name (Record ID) Method for estimating number of instances
CLPR Configuration (PD_CLPC) The number of cache partitions that exist in the storage system.
CLPR Per Controller Summary (PI_CLCS) (number-of-cache-partitions-that-exist-in-the-storage-system + 1) x (number-of-controllers-in-the-storage-system)
CLPR Summary (PI_CLPS) The number of cache partitions that exist in the storage system
LDEV Summary - Extended (PI_LDE) The number of logical devices that exist in the storage system, if the following storage system is monitored:
- Hitachi AMS2000 series
- HUS100 series
- Hitachi SMS series
Logical Device Aggregation (PI_LDA) Always 1.
Logical Device Configuration (PD_LDC)* The number of logical devices that exist in the storage system
Logical Device Summary (PI_LDS)* The number of logical devices that exist in the storage system
LUSE Configuration (PD_LSEC)* Among the logical devices that exist in the storage system, the number of logical devices that make up an expanded LU
Physical Device Operation Status (PI_PDOS) (number-of-disk-drives-that-exist-in-the-storage-system) x
(number-of-controllers-in-the-storage-system)
Pool Configuration (PD_PLC) The number of Dynamic Provisioning pools that exist in the
storage system
Pool Frequency Distribution Record (PD_PLF) (Number-of-Dynamic-Provisioning-pools-in-the-storage-system-that-perform-tier-management) x (number-of-partitions) (max. 496)

Note: This instance number is always 0 if the monitored storage system is not a HUS100 series.
Pool Page Relocation(PD_PLR) Number of Dynamic Provisioning pools in the storage system that perform tier management.

Note: This instance number is always 0 if the monitored storage system is not a HUS100 series.
Pool Summary (PI_PLS) The number of pools of Dynamic Provisioning that exists in the storage system

Note: This instance number is always 0 if the monitored storage system is not a HUS100 series or Hitachi AMS2000 series.
Pool Tier Page Relocation(PD_PLTR) (Number of Dynamic Provisioning pools in the storage system that perform tier management) x (Number of Tier that make up the Dynamic Provisioning pools that perform tier management)

Note: This instance number is always 0 if the monitored storage system is not a HUS100 series.
Pool Tier Type Configuration(PD_PLTC) (Number of Dynamic Provisioning pools in the storage system that perform tier management) x (Number of Tier that make up the Dynamic Provisioning pools that perform tier management)

Note: This instance number is always 0 if the monitored storage system is not a HUS100 series.
Pool Tier Type Operation Status(PD_PLTS) (Number of Dynamic Provisioning pools in the storage system that perform tier management) x (Number of Tier that make up the Dynamic Provisioning pools that perform tier management)

Note: This instance number is always 0 if the monitored storage system is not a HUS100 series.
Port Configuration (PD_PTC) The number of ports that exist in the storage system
Port Summary (PI_PTS) The number of ports that exist in the storage system
Processor Summary (PI_PRCS) The number of cores in processors that exist in the storage system.
RAID Group Configuration (PD_RGC) The number of parity groups that exist in the storage system.
If Dynamic Provisioning pools exist, the number of parity groups in the pools is also included.
RAID Group Summary (PI_RGS) The number of parity groups that exist in the storage system.
If Dynamic Provisioning pools exist, the number of parity groups in the pools is also included.
Storage Detail (PD) Always 1
Storage Summary (PI) Always 1
V-VOL Frequency Distribution Record (PD_VVF)  (Number-of-Dynamic-Provisioning-V-VOLs-in-the-storage-system-that-perform-tier-management) x (number-of-partitions) (max. 496)

Note:
This instance number is always 0 if the monitored storage system is not a HUS100 series.
V-VOL Tier Type Configuration(PD_VVTC)1 The following formula is use to calculate the number of instances for a Dynamic Provisioning pool that perform tier management in the storage system:
(The number of tiers that make up a Dynamic Provisioning pool that perform tier management) x (the number of V-VOLs that belong to the Dynamic Provisioning pool) (see notes below).
The total number of instances for a Dynamic Provisioning pool that perform tier management in the storage system will be the number of instances for this record.

Notes:

This instance number is always 0 if the monitored storage system is not a HUS100 series.
Virtual Volume Configuration (PD_VVC)* The number of Dynamic Provisioning V-VOLs that exist in the storage system
 *If the logical device definition file ldev_filter.ini is used, the number of instances for this record is the number of logical devices that satisfy the following two conditions:
  -The list of logical devices whose total number was calculated using the method described in Table 8 Defaults for
    number of stored records for each PD record type
  -The local device definition file