Upgrading to BigFix Inventory v10

BigFix Inventory is currently offered in single maintenance stream. Upgrading to the entire environment includes upgrading the BigFix Inventory server, VM Manager Tool, the scanner, and the database. For best results, update the server regularly to benefit from new capabilities and defect fixes. Once you finish the upgrade, you must restart all ongoing actions to enable the fixlets.

Before you begin

Ensure that no files or directories in the BigFix Inventory installation directory are open in an external program. For example, ensure that no log files are open in a text editor. Also, ensure that no PDF reports are being generated during the server upgrade. Otherwise, the upgrade might fail with error code 41.

For information about space requirements, see: Hardware requirements for the server on Windows or Hardware requirements for the server on Linux.
Important: For best results, especially for big environments, first run the fixlet in a test environment before you upgrade to check the component compatibility. To do so, back up your production database, restore it on the test server, and then upgrade. If the upgrade succeeds, upgrade the production server.

About this task

Note: You cannot upgrade between different operating systems.
For versions 9.2.14 or higher, you can directly upgrade to the latest version.
To upgrade to the latest version:
  1. Create a backup of the server. See Backing up the server.
  2. Upgrade the fixlet site. See Updating the fixlet site.
  3. Upgrade BigFix Inventory using fixlet: Upgrade to the latest version of BigFix Inventory.

  4. Migrate the database schema. See Updating the server database schema
  5. Upgrade all BigFix Inventory components, such as BigFix Inventory server, the database, VM Manager Tool, scanner and actions. See Upgrading the server in interactive mode, Upgrading the server in silent mode, Updating the server database schema, and Upgrading the scanner, tools and actions.
  6. In case schema migration fails, restore the server. See Restoring the server after a failed upgrade.
    Result: The BigFix Inventory server is upgraded to the latest version.
    Note: Run data import post upgrading the server.
For version lower than 9.2.14, it is not possible to upgrade directly to the latest version. To upgrade to the latest version, use the fixlet to upgrade to the interim version 10.0.2, migrate the database schema and then upgrade to the latest version.
To upgrade to the version 10.0.2:
  1. Create a backup of the server. See Backing up the server.
  2. Upgrade the fixlet site. See Updating the fixlet site.
  3. Upgrade BigFix Inventory using fixlet: Upgrade to the interim version 10.0.2 of BigFix Inventory if version older than 9.2.14.

  4. Migrate the database schema. See Updating the server database schema
  5. In case schema migration fails, restore the server. See Restoring the server after a failed upgrade.
    Result: The BigFix Inventory server is upgraded to interim version 10.0.2. To upgrade the server to the latest version, perform the steps mentioned above under the 'upgrade to the latest version' section.
    Note: Run data import post upgrading the server.

Upgrade considerations

New features and improvements may impact the existing capabilities. You need to take some additional steps or expect temporary longer duration of some processing.

About this task

Refer to the upgrade consideration when you upgrade from a specific version.
Table 1. Upgrade considerations
Version from which you are upgrading Considerations
Earlier than 10.0.2

The first data import after the upgrade takes longer, because the data includes the installation path of non-IBM software for existing records. This import is a one-time operation, and the next import takes the usual time to finish.

Information about the of scanned files is re-imported to show more details. The data is displayed on the "Scanned File Data" report in the "File Version" column.

Earlier than 9.2.11 The data is re-imported during a number of consecutive imports to avoid performance issues. Each consecutive import contains data from 10000 computers. The number of imports during which the data is re-imported is specified in the resync_imports parameter that is available by clicking Management > Advanced Server Settings.
Earlier than 9.2.1 If you had computer groups defined, subcapacity calculations are disabled for those groups after the upgrade. As a result, some of the panels and reports are not available to users who are assigned to those computer groups. To re-enable subcapacity calculations, click Management > Computer Groups, open a computer group, and select PVU, RVU MAPC, and VPC. Then, click Save. For more information, see: Setting up computer groups.