When Managing Devices with a Large Number of Volumes
When managing the following storage devices in which the number of volumes exceeds 18,000 per device, check whether the Management Server satisfies the CPU and memory required for behaviors of ETERNUS SF Manager.
ETERNUS DX900 S5
ETERNUS DX8900 S4
ETERNUS DX8000 S3/S2 series
For the CPU required for behaviors, refer to "Hardware Requirements" in "Operating Environment of ETERNUS SF Manager" in the Installation and Setup Guide.
For the memory required for behaviors, refer to "Estimating Memory Size When Using Large Numbers of Volumes" in the Installation and Setup Guide.
If the CPU and memory required for behaviors are not enough, it is required to add cores and memory to the Management Server.
In addition, when adding memory, it is also required to set memory to ETERNUS SF Manager, too. For setting method, refer to "Memory Settings to ETERNUS SF Manager When Using Large Numbers of Volumes" in the Installation and Setup Guide.
When Managing with Products That Use the RESTful API of the Storage Device
In system environments where this product shares storage devices with other products that use the RESTful API of the storage device, the operation must be designed so that each product does not perform a simultaneous configuration change operation of the shared storage device.
If a configuration change operation of the storage device is simultaneously performed from each product, one of the operations may terminate with an error. If the operation terminates with an error, after the operation is completed on the other side, try again.
Unit of Eco-mode Control
The Eco-mode can be controlled for each RAID group. Therefore, when different transactions (type, online time, etc.) use a RAID group, the disk drives of its RAID group may not be able to be stopped depending on the operating policy of the transaction. Consider the relation between RAID group and transactions in the design of the storage system operation using Eco-mode.
