Welcome
Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
Administering the database
Perform administering tasks on your database to keep it in good condition, protect your data, or configure additional settings.
Backing up and restoring the database
Perform regular backups of the data that is stored in the database, and restore it when needed to prevent data loss.

BigFix Documentation Homepage
BigFix 11 Inventory Documentation
Welcome to the BigFix Inventory documentation, where you can find information about how to install and configure BigFix Inventory. The application provides you with information about your inventory and license metrics. You can manage your software assets, gather information about your hardware, and ensure license compliance for your enterprise using BigFix Inventory.
BigFix Platform
Overview
Become familiar with key concepts that are necessary to understand how BigFix Inventory works and learn about features and functions that are introduced in every version of the application.
Installing
Learn about the requirements and available installation scenarios to ensure that the deployment of BigFix Inventory goes smoothly in your environment.
Configuring
After you install BigFix Inventory, configure the application. Create accounts for the users who need access to the application and set up scans to collect software and hardware inventory data from your environment.
Upgrading
A new version of BigFix Inventory is released periodically, typically at the end of each calendar quarter. Upgrade to the new version regularly to take full advantage of new features and application fixes.
Catalog Overview
This section provides information about catalog updates available with every release.
Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
- Computer statuses
  Computer statuses provide information about the condition of the computers that are monitored by BigFix Inventory. To properly discover the installed software and measure its license metric utilization, ensure that computers in your environment work correctly.
- Managing VM managers
  VM managers are pieces of software that create, manage, and monitor virtual machines. You configure connections to VM managers so that BigFix Inventory can gather data that is required to calculate utilization of license metrics in virtual environments.
- Administering the server
  Perform administering tasks on your server to configure advanced settings, or restart its services.
- Administering the database
  Perform administering tasks on your database to keep it in good condition, protect your data, or configure additional settings.
  - Backing up and restoring the database
    Perform regular backups of the data that is stored in the database, and restore it when needed to prevent data loss.
    - Backing up the DB2® database
      You should back up the database on a regular basis to protect your data. Each backup is the copy of the entire database that can be restored in the case of corruption or malfunction.
    - Restoring the DB2® database
      If your database has been corrupted or you want to revert some changes, you can restore it to its previous state from one of the backup files. Depending on the backup procedure that you chose, use either offline or online backup files. In the latter case, you must also restore the archive logs to make the database consistent.
    - Backing up the SQL Server database
      You can make a copy of your database by saving it to a backup file. If you want, you can then move the backup to another computer and restore it in a different BigFix Inventory instance.
    - Restoring the SQL Server database
      If you encounter any problems with your database or if you want to move it between different instances of BigFix Inventory, you can use a backup file to restore the database.
  - Creating a new database
    To create a new database without reinstalling BigFix Inventory, you must modify the configuration file that stores information about the database. After you do so, you will be able to complete the initial configuration again, and create a new database.
  - Reinstalling BigFix Inventory with an existing database
    You can reinstall BigFix Inventory and connect it to an existing database. This allows you to preserve all the data collected so far and avoid changing configuration settings.
  - Moving the BigFix Inventory database
    To move the BigFix Inventory database to a different computer, back up the database, move it to the target computer, and point to that computer in the server.xml and database.yml files.
  - Updating the database password
    You can update the database user password when needed, for example if the password is changed and users cannot log in to BigFix Inventory.
- Removing inactive computers
  When you decommission a computer in your infrastructure, it continues to report to BigFix Inventory. The data is still collected from this computer, and displayed on the metric reports. To ensure that all infrastructure changes are reflected in BigFix Inventory, you should remove each decommissioned computer from BigFix. If you cannot remove this computer from BigFix for a valid reason, you can use an alternative solution, and decommission the computer in BigFix Inventory.
- Managing data sources
  Computers in an organization can be divided into organizational units, and can be monitored by multiple BigFix infrastructures. Each infrastructure is referred to as a data source. Data from multiple data sources can be imported to one instance of BigFix Inventory.
Software inventory and license utilization
You can classify the discovered software so that reports in BigFix Inventory reflect your entitlements and properly show utilization of license metrics by particular products.
Managing security threats
Learn how to use BigFix Inventory to manage security threats in your environment. You can view whether any of the installed components is prone to any Common Vulnerability and Exposure (CVE).
Tutorials
Tutorials help you understand how to use BigFix Inventory. They consist of modules that focus on broad goals. Modules consist of tasks that show how to configure specific settings step-by-step.
Security
Configure different security features to adequately protect business assets and resources in the data model when using BigFix Inventory.
Troubleshooting and support
Learn about solutions to common problems that might arise when you use BigFix Inventory BigFix Inventory and how to find logs and trace files that help you troubleshoot those problems.
Tuning performance
Learn how to plan the infrastructure of BigFix Inventory and to configure the application server to achieve optimal performance. The following guidelines are applicable in big data environments as well as in smaller environments that are running on low-performance hardware.
Integrating with REST API
External systems integration is one of the key features of BigFix Inventory. Business logic is enabled for integration and interfaces are provided for common integration points.
Glossary
Guide in PDF format

Backing up and restoring the database

Perform regular backups of the data that is stored in the database, and restore it when needed to prevent data loss.

To maintain data consistency during data recovery, it is recommended to perform backup at least once per week. When you plan regular backups, you must consider the dynamics of your environment, for example, infrastructure changes and software installations. It is a good practice to back up the database before you update the software catalog, upgrade the server, or introduce significant changes to the middleware or the operating system. The number of backups that you keep depends on the storage space available. It is recommended to ensure that the backup that you store allows the restoration of your environment to the last functional state. Thus, if you introduce several consecutive changes in the application, the database, or the operating system, ensure that you perform backup after each of those change.

Consider the start time and duration of the import when you plan the backup schedule to avoid performance impact on the data import.