Disk space requirements for each installation directory (HTnM-Agent for NAS (When Hybrid Store is adopted))
return to main contents page
return to "Management server" contents page
Table 1 Disk space requirements shared by the Tuning Manager series for the entire system (Windows)
Status of Agent for RAID Disk space requirements (megabytes)
Windows Linux
During installation 1500 1352
Operating under
initial conditions
900 + a + 600(*1) 900 + a + 600(*1)
(*1) The disk space of 600 megabytes is shared by all agents running on the same host and whose database type is Hybrid Store. Therefore, when calculating the disk space requirements, add 600 megabytes for only one agent.
Legend:
a: Sum of the disk spaces for each instance
     The disk space requirement for a single instance can be calculated as follows:
     b + 78 + c (megabytes)
b: Disk space requirements for the Store database (megabytes)
For details, see Disk space requirements for Hybrid Store (HTnM-Agent for NAS).
c: Disk space requirements for the Alert Function (in megabytes)
The Alert Function stores a dump file of the memory on the disk. Thus, disk space requirements equal memory requirements. 
For details, see Memory requirements for the Alert Function.
Table 2 Disk space requirements shared by the Tuning Manager series for each installation directory
Directory name Status of Agent for RAID Disk space requirements (megabytes)
Windows Linux
%SystemDrive%
During installation 200 --
%TEMP% During installation 400 �@
Installation directory for Tuning Manager series programs During installation 900 --
Operating under initial
conditions
900 + a�@+ 600(*1) --
/opt/jp1pc During installation -- 900
Operating under initial
conditions
-- 900 + a + 600(*1)
/var During installation -- 2
/tmp During installation -- 450
(*1) The disk space of 600 megabytes is shared by all agents running on the same host and whose database type is Hybrid Store. Therefore, when calculating the disk space requirements, add 600 megabytes for only one agent.
Legend:
---:Not applicable
During Hitachi Data Ingestor monitoring (see Note)
a: Sum of the disk spaces for each instance
     The disk space requirement for a single instance can be calculated as follows:
     b + 78 + c (megabytes)
b: Disk space requirements for Hybrid Store (megabytes)
For details, see Disk space requirements for Hybrid Store (HTnM-Agent for NAS).
c: Disk space requirements for the Alert Function (in megabytes)
The Alert Function stores a dump file of the memory on the disk. Thus, disk space requirements equal memory requirements. 
For details, see Memory requirements for the Alert Function.
�@ �@ �@ �@
Note: Note that the following file servers are collectively called Hitachi Data Ingestor:
- Hitachi Data Ingestor
- Hitachi Capacity Optimization
- Hitachi NAS Platform F1000 Series
- Hitachi Essential NAS Platform
�@ �@ �@ �@
During NAS Platform monitoring
a: Sum of the disk spaces for each instance
     The disk space requirement for a single instance can be calculated as follows:
     b + 98 + c + d + e  (megabytes)
b: Disk space requirements for Hybrid Store (megabytes)
For details, see Disk space requirements for Hybrid Store (HTnM-Agent for NAS).
c: Disk space requirements for the directory for storing NAS Platform command execution results
     The disk space requirements for the directory for storing NAS Platform command execution results are calculated as follows:
     (1410 * v + 1560 * w) / 1024 (megabytes)
         v: Number of clusters in the NAS system
         w: Number of nodes in the NAS system
d: Disk space requirements for the directory for storing NAS Platform command execution results (for error files from the time of command execution)
     The disk space requirements for the directory for storing NAS Platform command execution results (for error files from the time of command execution) can be calculated as follows:
     (0.5 * v * x + 705 * v * y + 26 * w * z) / 1024 (megabytes)
       v: Number of clusters in the NAS system
       w: Number of nodes in the NAS system
       x: Value specified for smu.ver.err.limit in the agtn.properties file (threshold value for the number of folders that is used to decide whether to delete error folders for version information)
       y: Value specified for smu.conf.err.limit in the agtn.properties file (threshold value for the number of folders that is used to decide whether to delete error files for configuration information [excluding Share/Export])
       z: Value specified for smu.perf.err.limit in the agtn.properties file (threshold value for the number of folders that is used to decide whether to delete the number of error folders to retain for performance information)
e: Disk space requirements for the Alert Function (in megabytes)
The Alert Function stores a dump file of the memory on the disk. Thus, disk space requirements equal memory requirements. 
For details, see Memory requirements for the Alert Function.
When migration is performed from the Store database to Hybrid Store, free disk space might be required temporarily.
Before performing migration, confirm that there is enough free disk space by using the following estimate equation:
A = B * 0.2 + C
A: Free disk space that is temporarily required.
B: Total amount of the Store database size of all instances that are stored on the same disk.
C: The Store database size of the instance for which the required disk space is to be maximized, within the Store database stored on the same disk.
Note that when the Store database is stored on multiple disks, estimate the free disk space for each disk.
To check the size of the Store database, go to the services window of Performance Reporter, select the Agent Store service, and then from the Agent Store service properties window, select the Disk Usage node.
For details on how to confirm the Store database size, see the description for checking the amount of drive space used for performance data in the Tuning Manager Agent Administration Guide.
The default destination for storing the Store database is as follows:
For Windows:
installation-destination-folder\agtn\store\instance-name\
For UNIX:
/opt/jp1pc/agtn/store/instance-name/
If you have changed the storage destination folder of the Store database, use the jpcconf db define (jpcdbctrl config) command to confirm the location.