The following table contains guidelines for determining the size of your environment based on the number of monitoring targets. Based on the sizing and scalability guidelines, you can identify the hardware requirements and scale your environment to meet workload demands.
Monitoring storage systems only
| System scale | Maximum number of resources | ||
|---|---|---|---|
| Storage | |||
| Volume* | Storage | Volume Pair | |
| Small scale | 5,000 | 3 | 300 |
| Medium scale | 20,000 | 19 | 600 |
| Large scale | 50,000 | 30 | 1,200 |
| * Total number of volumes for all
storage systems. Note: To manage a system larger than that described in "Large scale", please contact us separately. |
|||
The system scale requirements for just monitoring storage systems are the same for all Ops Center products. For details, see the Hitachi Ops Center System Requirements.
Monitoring hypervisors and switches
| System scale |
Maximum number of resources | |||
|---|---|---|---|---|
| Hypervisor | FC Switch | |||
| ESX | VM | Switch | Total Port count | |
| Level 1 | 8 |
120 |
8 |
384 |
| Level 2 | 25 |
375 |
25 |
1,200 |
| Level 3 |
50 |
3,000 |
40 |
1,920 |
- a large number of volumes require a sizable database.
- if you decrease the interval at which you obtain performance information, the volumes occupy more disk space in the database.
Monitoring storage systems by using RAID Agent (Windows)
| System scale |
Maximum number of resources | |
|---|---|---|
| Storage | ||
| Storage | Volume | |
| Small scale |
1 |
5,000 |
| Medium scale |
5 |
35,000 |
| Large scale |
10 |
70,000 |
| Larger scale | 40 | 200,000 |
Use this table to perform hardware sizing based on the scale of the system to be monitored by using RAID Agent (Windows).
When using the Analyzer Adapter
|
System scale |
Maximum number of resources | |
|---|---|---|
| Storage | ||
| Storage | Volume | |
|
Extra Small scale |
2 |
1,000 |
|
Small scale |
5 |
5,000 |
|
Medium scale |
10 |
10,000 |
| Large scale | 30 | 50,000 |