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.
For operation as Express's manager
Directory name | Required disk space | Explanation |
|---|---|---|
Environment Directory | a + b | a: Database capacity of the repository for Manager. Refer to "3.1.4 Estimation of database size" for details. b: Repository size for common control. Refer to "Estimation formula for the repository size for common control" for details. |
Work Directory | c + 20(*1) | c: Required for performance management. Refer to "Disk space required for performance management" as described below for details. |
For performance management, add disk space as described below, depending on the number of Logical Units (LUs) on the storage device to be managed, the number of Disk Enclosures (DEs) and the number of days for which performance data are to be stored.
Storage Device | Required disk space (Unit: MB) |
|---|---|
ETERNUS DX60/DX60 S2 | 8 * (240 + (1.2 + 0.3 * DEs + 0.3 * (securedLUs + securedRAIDgroups [*1])) * 1440 + (95 * DEs) + (50 * (securedLUs + securedRAIDgroups [*1]))) / 1024 + 2.61 *1: RAIDgroups is the number of RAID groups created from LU. |
ETERNUS DX100 S3 | 8 * (475 + (1.2 + 0.7 * DEs + 0.4 * (securedLUs + securedRAIDgroups [*1])) * 1440 + (290 * DEs) + (76 * (securedLUs + securedRAIDgroups [*1]))) / 1024 + 2.25 *1: RAIDgroups is the number of RAID groups created from LU. |
Required size (MB) = 300 + (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)
For operation as Storage Cruiser's manager
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 the repository size for common control" for details. |
Work Directory | 55(*4) + 20(*5) + a + b | a: Repository size for common control. Refer to "Estimation formula for the repository size for common control" 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) = 300 + (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)
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 | 1862 | 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:
(1862 + (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:
(1862 + (32 * 1) + (80 * 0) + (115 * 0) + (100 * 2) + (306 * 4)) * 100
10 standard volumes in 1 RAID group which has 1 disk:
(1862 + (32 * 0) + (80 * 0) + (115 * 0) + (100 * 1) + (306 * 1)) * 10
a + b + c = 257400 bytes + 331800 bytes + 22680 bytes = 611880 bytes = about 598KB
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 | 10499 | 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 = 10499 + (630 * 1) + (646 * 1) = 11775 Volume configuration information1 = (383 * 2 + 234 + 895) * 4 = 7580 Volume configuration information2 = (383 * 4 + 356 + 895) * 10 = 27830 Report file size = 11775 + 7580 + 27830 = 47185bytes = about 46.1KB
For operation as AdvancedCopy Manager's manager
Directory Name | Required Disk Space | Explanation |
|---|---|---|
Environment Directory | For performing the backup operation:
| a: Number of backup volumes |
For performing the replication operation: (1.1 * d) / 1024 + e | ||
Work Directory | 1107 + f + 20(*1) | f: Capacity of saved file that is output according to "Volume lock error investigation function" in the ETERNUS SF AdvancedCopy Manager Operation Guide (for Windows). The output for each number of backup and transaction volumes and for each volume pair for replication management is made in sizes between several hundred KB and 2 MB each time an "in-use lock error" occurs. |
Database Creation Directory | g | g: Database capacity of the repository. Refer to "3.1.4 Estimation of database size" for details. |
f = (a + b + 2 * c) * 2(MB) * n(times)
Required size (MB) = 300 + (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)
For operating ETERNUS SF Manager, the server on which it is installed must add the following amount of memory.
When using neither Automated Storage Tiering nor Automated QoS function:
2.7GB
Other than those above:
3.7GB
For the manageable environment by ETERNUS SF Manager, refer to "Appendix G Upper Limit of Manageable Environment".
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 recommended by the operating system.