ETERNUS SF Express V16.6 / Storage Cruiser V16.6 / AdvancedCopy Manager V16.6 Installation and Setup Guide

2.2.6 Required Resources for Operation (for Operation as AdvancedCopy Manager's Manager)

2.2.6.1 Required Disk Space for Operation

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 Windows

Directory Name	Required Disk Space (Unit: MB)	Explanation
Environment Directory	For performing the backup operation: If not backing up the Symfoware: (a + 35 * b) / 1,024 + e + f If backing up the Symfoware: ((a + 35 * b) + (b + 0.5 * c)) / 1,024 + e + f	a: Number of backup volumes b: Number of transaction volumes c: Number of DSIs of all database spaces to be backed up d: Number of volume pairs for replication management e: Repository size for common control. Refer to "Estimation Formula for Repository Size for Common Control" for details. f: Database size for repository. Refer to "3.1.3 Estimation of Database Size" for details.
	For performing the replication operation: (1.1 * d) / 1,024 + e + f
Work Directory	1,107 + g + 20(*1)	g: 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. *1: Disk space required for the license management function

Assuming Size of 2 MB per Saved Volume File, for n Times "in-use lock error" Occurs, Capacity g is Determined by Following Formula

g = (a + b + 2 * c) * 2(MB) * n(times)

For Solaris

Directory Name	Required Disk Space (Unit: MB)	Explanation
/etc/opt	For performing the backup operation: (a + 35 * b) / 1,024 + 0.4	Add required disk space depending on your operation. a: Number of backup volumes b: Number of transaction volumes c: Number of volume pairs for replication management
	For performing the replication operation: (1.1 * c) / 1,024 + 0.4
/var	1,106	-
/var/opt	For non-clustered systems: 13 + e + f + 20(*1) For clustered systems: 26 + 4 * d + e + f + 20(*1)	d: Number of transactions (including local transactions) e: Database capacity of the repository. Refer to "3.1.3 Estimation of Database Size" for details. f: Repository size for common control. Refer to "Estimation Formula for Repository Size for Common Control" for details. *1: Disk space required for the license management function

For Linux

Directory Name	Required Disk Space (Unit: MB)	Explanation
/etc/opt	For performing the backup operation: If not backing up the Symfoware: (a + 35 * b) / 1,024 + 0.4 If backing up the Symfoware: ((a + 35 * b) + (b + 0.5 * c)) / 1,024 + 0.4	Add required disk space depending on your operation. a: Number of backup volumes b: Number of transaction volumes c: Number of DSIs of all database spaces to be backed up d: Number of volume pairs for replication management
	For performing the replication operation: (1.1 * d) / 1,024 + 0.4
/var	1,106	-
/var/opt	For non-clustered systems: 13 + f + g + 20(*1) For clustered systems: 26 + 4 * e + f + g + 20(*1)	e: Number of transactions (including local transactions) f: Database capacity of the repository. Refer to "3.1.3 Estimation of Database Size" for details. g: Repository size for common control. Refer to "Estimation Formula for Repository Size for Common Control" for details. *1: Disk space required for the license management function

Estimation Formula for Repository Size for Common Control

Required size (MB) = 400 + (servers + switches + devicesToBeManaged + disks + RAIDGroups + volumes) / 100 + (servers + switches + devicesToBeManaged) * users / 500

• servers : Number of Managed Servers

• switches : Number of switches to be managed

• devicesToBeManaged : Number of ETERNUS Disk storage systems to be managed

• disks : Total number of disks to be managed (Total number of disks in each ETERNUS Disk storage system to be managed)

• RAIDGroups : Total number of RAID groups to be managed (Total number of RAID groups that are created in each ETERNUS Disk storage system to be managed)

• volumes : Total number of volumes to be managed (Total number of volumes that are created in each ETERNUS Disk storage system to be managed)

• users : Number of users using Web Console (Number of user accounts)

2.2.6.2 Required Memory for Operation

For operating ETERNUS SF Manager, the server on which it is installed must add the following amount of memory.

• When the VMware vSphere Virtual Volumes function is not used

  4.1 GB

• When the VMware vSphere Virtual Volumes function is used

  6.2 GB

For the manageable environment by ETERNUS SF Manager, refer to "Appendix F Upper Limit of Manageable Environment".

When also operating Storage Cruiser's manager in the installation target server, refer to "2.2.5.2 Required Memory for Operation" in "Required Resources for Operation (for Operation as Storage Cruiser's Manager)".

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.

Note

Set swap memory. For capacity, set the value that is recommended by the operating system.