Hardware requirements

Hardware requirements for your Tivoli® Storage Manager 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 Selecting a system size.

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.

Hardware component	Small system	Medium system	Large system
Server processor	6 processor cores, 3.42 GHz or faster 12 processor cores, 1.9 GHz or faster	8 processor cores, 3.42 GHz or faster 16 processor cores, 2.0 GHz or faster	20 processor cores, 3.42 GHz 32 processor cores, 2.0 GHz or faster
Server memory	64 GB RAM	128 GB RAM	192 GB RAM
Network	10 GB Ethernet (1 port) 8 GB Fibre Channel adapter (2 ports)	10 GB Ethernet (2 ports) 8 GB Fibre Channel adapter (2 ports)	10 GB Ethernet (4 ports) 8 GB Fibre Channel adapter (4 ports)
Storage	1.3 TB inventory, plus space for Operations Center records 46 TB deduplicated directory-container storage pool	2 TB inventory, plus space for Operations Center records 200 TB deduplicated directory-container storage pool	4 TB inventory, plus space for Operations Center records 1000 TB deduplicated directory-container storage pool

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.

Managing the Operations Center on the server is a workload that requires extra space for database operations. The amount of space depends on the number of clients that are monitored on a server. Review the following guidelines to estimate how much space your server requires.

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.

Hardware requirements for the second server

If you are planning to set up your sites so that everything at the first site is replicated to the second site, hardware requirements are identical at both sites. If you want to only replicate a subset of data to your second site, storage and network requirements might be reduced.