Hardware requirements to support small, medium, and large environments

Notes

The recommended hardware requirements are valid, whether you use physical or virtual machines.
If you are installing the Infrastructure Management server in a virtual environment, ensure to reserve CPU and memory resources.
BMC recommends a tier 1 SAN storage (2-4 GBps SAN dedicated channel) for the BMC TrueSight Infrastructure Management Server.

Related topics

Hardware requirements for the Infrastructure Management Server with the embedded SAP SQL Anywhere database

Consider the following hardware requirements for a SAP SQL Anywhere database server when you are planning the size of your environment for data event management, and impact event management.

Infrastructure Management Server hardware requirements when using an embedded SAP SQL Anywhere database

Environment	Configuration Item	Data event management and impact event management
Small	Platform	Windows 2008 R2 (64-bit), Intel Core i7 CPU: 4 vCPU, Frequency: 2.2 GHz SPARC Enterprise T-Series or M-Series Servers CPU: 4 CPUs, of 3 GHz, UltraSPARC T2 Linux 2.6.32-358.18.1.el6.x86_64 CPU: 4 vCPU, Frequency: 2.2GHz
	RAM	8 GB
	Storage configuration	200 GB (30 GB for the server + 170 GB for the database) 15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)
Medium	Platform	Windows 2008 R2 (64-bit), Intel Core i7 CPU: 4 vCPU, Frequency: 2.2 GHz SPARC Enterprise T-Series or M-Series Servers CPU: 4 CPUs, 3 GHz, UltraSPARC T2 Linux 2.6.32-358.18.1.el6.x86_64 CPU: 4 vCPU, Frequency: 2.2GHz
	RAM	16 GB An additional 4 GB of RAM is required if you are using the BMC-supplied SAP SQL Anywhere database.
	Storage configuration	300 GB (50 GB for the server + 250 GB for the database) 15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)
Large	Platform	Windows 2008 R2 (64-bit), Intel Core i7 CPU: 8 vCPU, Frequency: 2.2GHz SPARC Enterprise T-Series or M-Series Servers CPU: 8 CPUs, 3 GHz, UltraSPARC T2 Linux 2.6.32-358.18.1.el6.x86_64 CPU: 8 vCPU, Frequency: 2.2GHz
	RAM	32 GB An additional 8 GB of RAM is required if you are using the BMC-supplied SAP SQL Anywhere database.
	Storage configuration	600 GB (100 GB for the server + 500 GB for the database) 15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)

Hardware requirements for an Oracle database server

Consider the following hardware requirements for an Oracle database server when you are planning the size of your environment for data event management, and impact event management. For information about supported databases, see Supported databases and Web consoles requirements for Infrastructure Management.

Infrastructure Management Oracle database server hardware requirements

Environment	Configuration Item	Requirement
Small	Platform	Windows 2008 R2 (64-bit), Intel Core i7 CPU: 4 vCPU, Frequency: 2.2GHz SPARC Enterprise T-Series or M-Series Servers CPU: 4 CPUs, of 3 GHz, UltraSPARC T2 Linux 2.6.32-358.18.1.el6.x86_64 CPU: 4 vCPU, Frequency: 2.2GHz
	RAM	16 GB
	Storage configuration	170 GB for the database 15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)
Medium	Platform	Windows 2008 R2 (64-bit), Intel Core i7 CPU: 4 vCPU, Frequency: 2.2GHz SPARC Enterprise T-Series or M-Series Servers CPU: 4 CPUs, 3 GHz, UltraSPARC T2 Linux 2.6.32-358.18.1.el6.x86_64 CPU: 4 vCPU, Frequency: 2.2GHz
	RAM	32 GB
	Storage configuration	250 GB for the database 15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)
Large	Platform	Windows 2008 R2 (64-bit), Intel Core i7 CPU: 4 vCPU, Frequency: 2.2GHz SPARC Enterprise T-Series or M-Series Servers CPU: 8 CPUs, 3 GHz, UltraSPARC T2 Linux 2.6.32-358.18.1.el6.x86_64 CPU: 8 vCPU, Frequency: 2.2GHz
	RAM	32 GB
	Storage configuration	500 GB for the database 15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)

Hardware requirements for an Infrastructure Management Server with an Oracle database

Consider the following hardware requirements for the computer on which the Infrastructure Management Server is installed when it is configured with an Oracle database.

Infrastructure Management Server hardware requirements when using an Oracle database

Environment	Configuration Item	Data event management and impact event management
Small	Platform	Windows 2008 R2 (64-bit), Intel Core i7 CPU: 4 vCPU, Frequency: 2.2 GHz SPARC Enterprise T-Series or M-Series Servers CPU: 4 CPUs, of 3 GHz, UltraSPARC T2 Linux 2.6.32-358.18.1.el6.x86_64 CPU: 4 vCPU, Frequency: 2.2GHz
	RAM	8 GB
	Storage configuration	30 GB 15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)
Medium	Platform	Windows 2008 R2 (64-bit), Intel Core i7 CPU: 4 vCPU, Frequency: 2.2 GHz SPARC Enterprise T-Series or M-Series Servers CPU: 4 CPUs, 3 GHz, UltraSPARC T2 Linux 2.6.32-358.18.1.el6.x86_64 CPU: 4 vCPU, Frequency: 2.2GHz
	RAM	16 GB
	Storage configuration	50 GB 15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)
Large	Platform	Windows 2008 R2 (64-bit), Intel Core i7 CPU: 8 vCPU, Frequency: 2.2GHz SPARC Enterprise T-Series or M-Series Servers CPU: 8 CPUs, 3 GHz, UltraSPARC T2 Linux 2.6.32-358.18.1.el6.x86_64 CPU: 8 vCPU, Frequency: 2.2GHz
	RAM	32 GB
	Storage configuration	100 GB for the server 15000 RPM drive or a tier 1 SAN storage (2-4 GBps SAN dedicated channel)

Database considerations

Infrastructure Management can use the embedded SAP SQL Anywhere ASA database or an Oracle database in any deployment:

An embedded SAP SQL Anywhere database must run on the same system as the core server components. The embedded database is optimized for Infrastructure Management.
An Oracle database must run on a different system within the same subnet network.

Disk subsystems and database performance best practices

The performance of the disk subsystem used for the database can significantly affect the scalability of your system. To optimize performance, BMC recommends the following guidelines:

Use RAID 10 or 01 on larger Infrastructure Management installations to better satisfy the higher demands on write I/O operations. BMC does not recommend using RAID 5.
Use SAN on medium and large deployments.
Use a larger number of physical disk drives (spindle count) than capacity disks. Because disk drive throughput performance has not increased at the same rate as disk capacity, you can achieve better performance with smaller disks.
For large environments, run a defragmentation process on the database file every six months.
Avoid extending raw data retention past recommended guidelines because this can impact I/O performance. For recommended guidelines, see the following topics:
BMC performance testing for sizing was performed on UNIX and NTFS file system. Performance problems were observed using Veritas file systems, and BMC does not recommend those file systems for large deployments. For information about database performance benchmarks and tuning recommendations, see the following topics:

CPU guidelines

Parallel CPUs usually improve user response time better than a single CPU with a higher clock speed.

Guidelines and limitations for deployment

Follow these guidelines when planning the hardware deployment:

You can run multiple Integration Service processes on the same computer. Each Integration Service process on a computer requires 3 GB to 4 GB of memory.
The computers on which the Administration Console or the Operations Console are installed and the computer in which the BMC TrueSight Infrastructure Management Server is installed should be running on the same network. To avoid a performance issue on the BMC TrueSight Infrastructure Management Server, do not open the Administration Console or the Operations Console on the the BMC TrueSight Infrastructure Management Server. Open these consoles on a computer other than the computer on which the BMC TrueSight Infrastructure Management Server is running.
BMC recommends that the BMC TrueSight Infrastructure Management server be a dedicated server with no other products installed on it.
BMC recommends a maximum of three Integration Service instances running on a single Integration Service host computer. For more information, see Sizing chart for multiple Integration Services running on the same Integration Service host.