Storage sizing recommendations

This topic provides guidelines for estimating data storage requirements for a BMC Server Automation installation.

Database sizing

Many factors influence the amount of storage consumed by the database that supports a BMC Server Automation installation. Factors of particular importance are:

• Number of managed servers
• Number and frequency of jobs run for each target
• Required retention period for historic job run data

For new installations for which no previous baseline data is available, BMC suggests a planning figure of 15 MB per managed server as a very general guideline for configuring the BMC Server Automation database server. However, you can use the following database sizing recommendations as starting points for your sizing exercise.

Note that the environment size depends on the number of managed targets, the use-cases you are implementing, and the expected job runtimes.

Patch repository sizing

BMC Server Automation patch content, which is stored in patch repositories, varies in size depending on application and vendor. The following table presents patch storage requirements for various Microsoft applications, as observed in November 2011.

Local storage requirements

Major patch deployments for Oracle Solaris and IBM AIX operating systems can require about 1 GB of local storage under /var/tmp on each host to be patched.