Hardware Requirements - Documentation for Bmc Client Management 12.9

The following sections provide a quick overview of the minimum hardware requirements for the different components of BMC Client Management. For more detailed information and specific database recommendations refer to Database tuning.

Hardware requirements for the master, database, and relays

This table lists the recommended hardware per node count. It is important to understand that this document generalizes the hardware recommendations and the hardware requirements can be more or less for any given environment. When running in virtual environments, CPU, RAM, and NIC utilization on the host system can impact performance. Dedicated physical CPU, RAM, and NIC cards can improve performance.

These estimations are for infrastructures in which a Windows relay has a maximum of 2000 child nodes or a Linux relay has 5000 child nodes.

Hardware sizing recommendations

The following table lists sizing recommendations for the dedicated hardware resources required by the server database, depending on the number of nodes.

Number of nodes

Memory

CPU/Core/Speed/Cache

Estimated database size

20,000

16 GB

2/4/2 GHz/8.0 MB

20 GB

50,000

24 GB

2/4/3 GHz/12 MB

50 GB

100,000

48 GB

2/8/3 GHz/20 MB

100 GB

150,000

72 GB

2/8/3 GHz/20 MB

150 GB

200,000

96 GB

2/8/3 GHz/20 MB

200 GB

Evaluation or <500 nodes

Master server

Each relay 2,3

Dedicated database 4

CPU

1

Dedicated relay should not be required 1

Dedicated database should not be required

Core2
Speed2 GHz
Cache2 MB
RAM4 GB
Estimated size50 Gb

<20,000 nodes

Master server

Each relay 2,3

Dedicated database 4

CPU

1

1

2

Core

4

4

4

Speed

2 GHz

2 GHz

2 GHz

Cache

8 MB

8 MB

8 MB

RAM

8 GB

8 GB

16 GB

Disk size for Client Management data storage

200 GB free space, 15k RPM or faster drives 5

200 GB 5

20 GB 6

<50,000 nodes

Master server

Each relay 2,3

Dedicated database 4

CPU

1

1

2

Core

4

4

4

Speed

2 GHz

2 GHz

3 GHz

Cache

8 MB

8 MB

12 MB

RAM

16 GB

8 GB

24 GB

Disk size for Client Management data storage

200 GB free space, 15k RPM or faster drives 5

200 GB 5

50 GB 6

<100,000 nodes

Master server

Each relay 2,3

Dedicated database 4

CPU

1

1

2

Core

4

4

8

Speed

2 GHz

2 GHz

3 GHz

Cache

8 MB

8 MB

20 MB

RAM

16 GB

8 GB

48 GB

Disk size for Client Management data storage

200 GB free space, 15k RPM or faster drives 5

200 GB 5

100 GB 6

<150,000 nodes

Master server

Each relay 2,3

Dedicated database 4

CPU

1

1

2

Core

4

4

8

Speed

2 GHz

2 GHz

3 GHz

Cache

8 MB

8 MB

20 MB

RAM

16 GB

8 GB

72 GB

Disk size for Client Management data storage

200 GB free space, 15k RPM or faster drives 5

200 GB 5

150 GB 6,7

<200,000 nodes

Master server

Each relay 2,3

Dedicated database 4

CPU

1

1

2

Core

4

4

8

Speed

2 GHz

2 GHz

3 GHz

Cache

8 MB

8 MB

20 MB

RAM

16 GB

8 GB

96 GB

Disk size for Client Management data storage

200 GB free space, 15k RPM or faster drives 5

200 GB 5

200 GB 6,7

  1. Required disk space varies based on size of deployed packages, patches and service packs.
  2. Number of relays required varies based upon network topology and other environmental factors.
  3. These estimations are for infrastructures in which a Windows relay has a maximum of 2000 child nodes or a Linux relay has 5000 child nodes.
  4. Check with the database vendor to identify any hardware limitations based upon the version in use. Your licensed database version cannot utilize all hardware resources, for example, Microsoft SQL Express, Microsoft SQL Workgroup, Oracle Express.
  5. The size of the disk space depends on the BMC Client Management features you are using. For example, if you are using Patch Management (including several Windows 10 versions and languages) or big software distribution or your relay is configured as OSD Image Repository (several images of 8 GB each), you might need more disk space.
  6. This is the estimated disk size for storing only Client Management generated data. For detailed information on the required database size and best practices see Database tuning.
  7. BMC recommends and Oracle or PostgreSQL database on Linux for better performance, but an SQL Server database is also possible to use SQL Server.
James H. Sterling

James H. Sterling

Environmental Science & Climate Journalist

James Sterling reports on renewable energy developments, climate policy, ecological conservation, and green tech innovations around the globe.

Share this article
Twitter Facebook Pinterest