Disk space requirements on Linux (BigFix scenario)

Ensure that the computer on which you are installing License Metric Tool meets the minimal disk space requirements.

Important: The BigFix® client is also installed on the computers where the components are installed. Ensure that the computers have enough space for the client. For more information, see: Disk space requirements for the BigFix client (BigFix scenario).

Simplified disk space requirements

The following table shows general disk space requirements depending on the number of endpoint units. To learn more about directories in which the free disk space is required and how to calculate the amount of space for data that depends on the number of computers, see the following sections.

Table 1. Simplified disk space requirements
Endpoint units License Metric Tool server, its database, and BigFix on a single computers License Metric Tool server and its database on a single computer
Up to 1 000 60 GB 46 GB
1 000 - 5 000 72 GB 56 GB
5 000 - 25 000 136 GB 113 GB
25 000 - 50 000 Set up with the License Metric Tool server and database on a single computer and BigFix on a separate computer is advised. 192 GB
50 000 - 150 000 Set up with the License Metric Tool server, database and BigFix on separate computers is advised. Set up with the License Metric Tool server on one computer and its database on a separate computer is advised due to processor, memory, and storage requirements.
  • Computer with the License Metric Tool server: 7 GB
  • Computer with the database: 505 GB
150 000 - 250 000 Set up with the License Metric Tool server, database and BigFix on separate computers is advised. Set up with the License Metric Tool server on one computer and its database on a separate computer is advised due to processor, memory, and storage requirements.
  • Computer with the License Metric Tool server: 7 GB
  • Computer with the database: 825 GB

Disk space requirements for the All-in-One installation

The following table shows simplified disk space requirements for the All-in-One installation of License Metric Tool. For more detailed requirements for each component, see: Detailed disk space requirements for the License Metric Tool server.

Table 2. Disk space requirements for the All-in-One installation
Computer Default Directory Space required Comments
Computer 1 on Linux /opt 10 GB The License Metric Tool server, DB2 database and some components of BigFix.
/var 10 GB BigFix server.
/home 50 GB Database content.
/root 10 GB Compressed installer that is downloaded to the selected endpoint from BigFix and the installer after it is extracted. The compressed installer can be deleted after it is extracted.
Important: All-in-One installation does not support a non-root installation.
/tmp 1 GB Temporary files used during the installation.
Important: The installer must be able to run executable files in this directory.
Computer 2 on Windows C:\Program Files\BigFix Enterprise\BES Console 90 MB BigFix console installation directory. The console must be installed on Windows.

Detailed disk space requirements for the License Metric Tool server

Table 3. Detailed disk space requirements for the License Metric Tool server
Default Directory Space required Comments
/root/LMT_installer 1 GB Compressed installer that is downloaded to the selected endpoint from BigFix. The compressed installer can be deleted after it is extracted.
2 GB Extracted installation files.
/etc 1 MB Directory that stores scripts that start the server.
/opt/ibm/LMT 4 GB License Metric Tool installation directory. The amount includes space required for future upgrades.
/tmp 350 MB Temporary files used during the installation.
Important: The installer must be able to run executable files in this directory.
/var 10 kB Directory that stores the installation registry.
$HOME 1 MB Home directory of the user running the installation.

Detailed disk space requirements for DB2 for License Metric Tool

Table 4. Detailed disk space requirements for DB2 for License Metric Tool
Default Directory Space required Comments
/home/db2fenc1 1 MB Home directory of the DB2 fenced user.
/home/db2inst1 See Comments Database server instance.
The amount of disk space that is required for the database server depends on the number of computers in your environment and the average size of scan files and analysis. It can be calculated according to the following formula*:
  • <The number of computers> x 1 MB + 15 GB of initial disk space
For example:
10 000 computers
10 000 x 1 MB + 15 GB = 25 GB
100 000 computers
100 000 x 1 MB + 15 GB = 115 GB
/home/db2inst1/db2inst1 See Comments Database server transaction logs.
During the data import (ETL process), License Metric Tool requires some additional free disk space for database server transaction logs. The amount of disk space that is required can be significant because transaction logs store two sets of data:
  • Data that is used for recovery if the ETL fails
  • Data that is used to create new ETL results
The amount of disk space that is necessary for the transaction logs depends on the number of computers in your environment as well as the number of computers in a single scan group from which data is processed during the import.

To lower the amount of disk space that is necessary for transactions logs, distribute the scans over time so they are processed during several data imports instead of one.

The size of transaction logs can be calculated according to the following formula*:
  • <The number of computers> x 1.2 MB + <the number of computers in the biggest scan group> x 1.2 MB + 17 GB of initial disk space
For example:
10 000 computers and 10 000 scan results
10 000 x 1.2 MB + 10 000 x 1.2 MB + 17 GB = 41 GB
100 000 computers and 15 000 scan results
100 000 x 1.2 MB + 15 000 x 1.2 MB + 17 GB = 155 GB
/opt/IBM/db2 1.5 GB DB2 installation directory.
/var/db2 10 kB Directory that stores DB2 global registry.
/var/log 1 MB Directory with log files.
* The formulas apply to typical environments that are configured to run weekly software scans, daily data imports, and whose endpoints have about 60 software installations each. The results also depend on the amount of data returned by the scans, which means that in some environments the required amount of disk space might be smaller or bigger. In case of irregular data imports or accumulated scans, the required disk space increases.
Note: The retention period in this typical environment is set to the last 7 days. For more information about tuning this parameter, see: Shortening the retention period gradually to avoid problems with growing database size.

Detailed disk space requirements for BigFix

Table 5.
Default Directory Space required Comments
/var/opt/BESInstallers 90 MB Directory with console and client installers.
/var/opt/BESServer 2 GB BigFix installation directory.
/var/opt/BESServer/wwwrootbes/bfmirror/downloads/sha1/ Around 3 GB BigFix cache. It stores files that are downloaded by some of the fixlets before they are distributed to the selected endpoints. For example, the License Metric Tool installer.

The required space might increase if you run some of the fixlets multiple times. For example, each time you run the Upgrade to the latest version of IBM License Metric Tool 9.x, a new installer is downloaded to the cache. Thus, the required space increases.

To check whether a fixlet downloads any files and what their size is, log in to the BigFix console, and check the value in the Download Size column for the particular fixlet. Then, ensure that enough disk space is available in the BigFix cache.

/var/opt/BESWebReportsServer 300 MB Web Reports installation directory.
/opt/BESWebReportsServer 50 MB Directory with the Web Reports server binaries.
/opt/BESServer 100 MB Directory with server binaries.
3 GB Temporary space for server binaries. The space is needed only when you are using the All-in-One installer.
/var/log 1 MB Directory with log files.
C:\Program Files\BigFix Enterprise\BES Console 90 MB BigFix console installation directory. The console must be installed on Windows.

For disk speed, see: Storage performance requirements.

Disk space requirements for DB2 for BigFix

For information about hardware requirements for DB2 that is used as the BigFix database, see the Database requirements.

Apart from the disk space that is described in the guide, ensure additional disk space for transaction logs on the computer where the BigFix database is installed. To calculate the required disk space, check how many objects exist in all fixlet sites that you have enabled in the BigFix console. An object is every computer group, analysis, fixlet, and task that exist in the console, including the ones that are not relevant. Every 1000 objects requires 1GB of free disk space. For example, if you have 500 fixlets and tasks, 300 analyses, and 20 computer groups, you have 820 objects in total. Thus, 1 GB of disk space is required.