Hardware requirements
Hardware requirements for your IBM Spectrum Protect solution are based on system size. Choose equivalent or better components than those items that are listed to ensure optimum performance for your environment.
For a definition of system sizes, see t_msdisk_select_size.html.
The following table includes minimum hardware requirements for the server and storage, based on the size of the server that you plan to build. If you are using local partitions (LPARs) or work partitions (WPARs), adjust the network requirements to take account of the partition sizes.
Use the information in the following table as a starting point. For the most up-to-date information about hardware requirements and specifications for the server and storage, see the IBM Spectrum Protect Blueprints.
| Hardware component | Small system | Medium system | Large system |
|---|---|---|---|
| Server processor |
|
|
|
| Server memory | 64 GB RAM | 128 GB RAM | 256 GB RAM |
| Network |
|
|
|
| Storage |
|
|
|
6 processor cores, 3.42 GHz or faster
16 processor cores, 1.7 GHz or fasterImplementing the correct processor core technology
You must use the correct type of processor core technology for the server processor. For information about the type of processor core technology, see the IBM Spectrum Protect Blueprints.
Estimating database space requirements for the Operations Center
Hardware requirements for the Operations Center are included in the preceding table, except for the database and archive log space (inventory) that the Operations Center uses to hold records for managed clients.
If you do not plan to install the Operations Center on the same system as the server, you can estimate system requirements separately. To calculate system requirements for the Operations Center, see the system requirements calculator in technote 1641684.
- Database space
- The Operations Center uses approximately 1.2 GB of
database space for every 1000 clients that are monitored on a server. For example, consider a hub
server with 2000 clients that also manages three spoke servers, each with 1500 clients. This
configuration has a total of 6500 clients across the four servers and requires approximately 8.4 GB
of database space. This value is calculated by rounding the 6500 clients up to the next closest
1000, which is 7000:
7 x 1.2 GB=8.4 GB
- Archive log space
- The Operations Center uses approximately 8 GB of archive
log space every 24 hours, for every 1000 clients. In the example of 6500 clients across the hub
server and the spoke servers, 56 GB of archive log space is used over a 24-hour period for the hub
server.For each spoke server in the example, the archive log space that is used over 24 hours is approximately 16 GB. These estimates are based on the default status collection interval of 5 minutes. If you reduce the collection interval from once every 5 minutes to once every 3 minutes, the space requirements increase. The following examples show the approximate increase in the log space requirement with a collection interval of once every 3 minutes:
- Hub server: 56 GB to approximately 94 GB
- Each spoke server: 16 GB to approximately 28 GB
Increase the archive log space so that you have sufficient space available to support the Operations Center, without affecting the existing server operations.