For operating ETERNUS SF Manager, in addition to disk space described in "2.2.3.1 Required Disk Space for Installation", the server on which it is installed must have free disk space as described below.
Directory Name | Required Disk Space | Explanation |
|---|---|---|
Environment Directory | 5 + 1(*1) + 1.2(*2) + 65(*3) + a | a: Repository size for common control. Refer to "Estimation Formula for Repository Size for Common Control" for details. |
Work Directory | 55(*4) + 20(*5) + a + b + c | a: Repository size for common control. Refer to "Estimation Formula for Repository Size for Common Control" for details. |
Directory Name | Required Disk Space | Explanation |
|---|---|---|
/etc/opt/FJSVssmgr | 5 + 1(*1) + 1.2(*2) + 65(*3) | *1: Configuration definition file - Calculated assuming a maximum of a 100 products. |
/var/opt/FJSVssmgr | 55(*4) + a | a: Repository for Storage Cruiser |
/var/opt/FJSVesfcm | b | b: Repository size for common control. Refer to "Estimation Formula for Repository Size for Common Control" for details. |
/var/opt/FJSVesflm | 20 | Disk space required for the license management function |
/var/opt/FJSVssast | c | c: Disk space required when using Automated Storage Tiering. Refer to "Disk Space Required When Using Automated Storage Tiering" for details. |
Add the total of disk space as described below, depending on the numbers of storage devices to be managed.
|
Additionally, for performing the performance management, disk space is necessary depending on the number of devices from which to collect performance data and the number of days for which performance data are to be stored. Refer to "Appendix C Required Disk Space for Performance Management" for details.
Required size (MB) = 400 + (servers + switches + devicesToBeManaged + disks + RAIDGroups + volumes) / 100 + (servers + switches + devicesToBeManaged) * users / 500 |
servers : Number of Managed Servers
switches : Number of managed switches
devicesToBeManaged : Number of managed ETERNUS Disk storage systems
disks : Total number of disks in each managed ETERNUS Disk storage system
RAIDGroups : Number of managed RAID groups
volumes : Number of managed volumes
users : Number of users using Web Console (Number of user accounts)
Depending on the total capacity of the target Tier pool, add the following capacity when performing an Automated Storage Tiering.
Required size (MB) = 27 * total capacity of the Tier pool (unit:TB) |
The following is a description of the resources such as size and tuning required to use this function:
Resource | Condition |
|---|---|
Information stack file | There is no upper limit to accumulated data size (dependent on disk space). Retention period can be set in the policy file. Data can be retained up to 10 years. If the retention period set in the policy file is exceeded, the data is deleted when creating a report. |
Report file | There is no upper limit to file size. |
It is required to estimate the sizes of the following files:
Information stack file: File in which report information is accumulated by the reporting information collection command.
Report file: File output by the report creation command.
File size can be roughly estimated from data amount per month and retention period as shown in the following estimate formula.
Data amount per month can be found by adding up the sum of volume configuration information size at month's outset per volume and the sum of one-month updated/added volume configuration information size per volume.
In the following estimate formula, the sum per volume is expressed as "SIGMA".
In addition, volume configuration information size can be found by the following calculation formula.
Information stack file capacity = (data amount per month) * retention period [month]
(unit: byte)
Data amount per month = SIGMA(volume configuration information size at month's outset) +
SIGMA(one-month updated/added(*1) volume configuration information size)
*1: Even if the volume is deleted halfway, the target volume information for the month
is not deleted.
Volume configuration information size = 1862 +
(32 * number of Thin Provisioning Pools) +
(80 * number of Tier pools) +
(115 * number of Tier sub-pools) +
(100 * number of RAID groups) +
(306 * number of disks)The breakdown of volume configuration information size is as follows.
Item | Size (byte) | Number of Records |
|---|---|---|
Basic information | 1,862 | Fixed |
Thin Provisioning information | 32 | Number of Thin Provisioning Pools |
Tier pool information | 80 | Number of Tier pools |
Tier sub-pool information | 115 | Number of Tier sub-pools |
RAID information | 100 | Number of RAID groups |
Disk information | 306 | Number of disks allocated to RAID groups |
The following is an estimate example of one-month file size when Volumes a and b are already created at month's outset and Volume c is added halfway:
100 standard volumes in 1 RAID group which has 2 disks:
(1,862 + (32 * 0) + (80 * 0) + (115 * 0) + (100 * 1) + (306 * 2)) * 100
100 TPV volumes in 1 Thin Provisioning Pool comprised of 2 RAID groups each with 4 disks:
(1,862 + (32 * 1) + (80 * 0) + (115 * 0) + (100 * 2) + (306 * 4)) * 100
10 standard volumes in 1 RAID group which has 1 disk:
(1,862 + (32 * 0) + (80 * 0) + (115 * 0) + (100 * 1) + (306 * 1)) * 10
a + b + c = 257,400 bytes + 331,800 bytes + 22,680 bytes = 611,880 bytes = about 598 KB
File size depends on storage configuration (on the number of disks and volumes allocated to RAID groups). Report file size can be roughly estimated from basic information and sum of volume configuration resource size per volume as shown below.
In the following estimate formula, the sum per volume is expressed as "SIGMA":
Report file capacity = basic information + SIGMA(volume configuration resource size)
(unit: byte)
- Basic information = header information +
(server information * number of servers connected to volumes) +
(disk storage system information * number of disk storage systems (*1))
*1: Where one disk storage system is being allocated to multiple server volumes,
the disk storage systems are counted in terms of the number of servers.
- Volume configuration resource size =
(disk information * number of disks in volume allocated
RAID group + volume type information + volume information) * number of volumes
connected to server.The size and number of records are roughly estimated as follows.
Category | Record Name | Size (byte) | Number of Records |
|---|---|---|---|
Basic information | Header information | 10,499 | 1 (fixed) |
Server information | 630 | Number of servers connected to volumes | |
Disk storage system | 646 | Number of disk storage systems including volumes used by server | |
Volume config. resources | Disk information | 383 | Number of disks allocated to RAID groups |
Volume type information | 234 (Standard/SDV/WSV) | Number of RAID groups/Thin Provisioning Pools/Tier pools | |
Volume information | 895 | Number of volumes connected to server |
The following is an estimate example of report file size when creating volumes under the following conditions:
The number of servers connected to volumes is 1.
The number of disk storage systems is 1.
"Volume configuration resource1"
Create 4 standard volumes in a RAID group using 2 disks.
"Volume configuration resource2"
Create a RAID group using 4 disks in Thin Provisioning Pool and create 10 TPV volumes.
Connect the created volumes to the server.
Basic information = 10,499 + (630 * 1) + (646 * 1) = 11,775 Volume configuration information1 = (383 * 2 + 234 + 895) * 4 = 7,580 Volume configuration information2 = (383 * 4 + 356 + 895) * 10 = 27,830 Report file size = 11,775 + 7,580 + 27,830 = 47,185 bytes = about 46.1 KB
For operating ETERNUS SF Manager, the server on which it is installed must add the following amount of memory.
When either Automated Storage Tiering, the Automated QoS function, or the VMware vSphere Virtual Volumes function is not used
4.1 GB
Other than the above
6.2 GB
For the manageable environment by ETERNUS SF Manager, refer to "Appendix F Upper Limit of Manageable Environment".
When managing the ETERNUS DX8000 S3 series, DX8000 S2 series in which the number of volumes exceeds 18,000 per device, it is required to add more memory to the above listed memory. Refer to "Appendix J Adding Memory to ETERNUS SF Manager When Using Large Numbers of Volumes" for information on how to estimate and set up memory size.
If Automated Storage Tiering is used, in addition to the above memory size, additional memory must be added to the install target server in accordance with the total value of the total capacity of Tier pools. Refer to "F.2 Upper Limit of Automated Storage Tiering" for information on how to estimate and set up memory size.
Note
When using the Automated Storage Tiering, the case of using one layer Tier pool is also included.
Set swap memory. For capacity, set the value that is recommended by the operating system.