Home
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.
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.
Restoring the server after a failed upgrade
After a failed upgrade, you can restore the server to its original state by restoring the database, installation registry, and the server files from backups.

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.
- 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.
  - Updating the fixlet site
    The content of the BigFix Inventory fixlet site can be periodically modified. New fixlets, tasks, and analyses can be added. The existing ones can be changed or might become obsolete due to functionality changes. If the BigFix server is installed on a computer with the Internet access, the BigFix Inventory fixlet site is updated automatically whenever the updates are available. However, if the server is installed on a computer without the Internet access, you must update the fixlet site manually. Start by checking whether the fixlet site that you are currently using is up-to-date. If a newer version of the fixlet site exists, download the site content by using the Airgap tool. Then, cache the files on the BigFix server by using the BES Download Cacher.
  - Backing up the server
    Before you start the upgrade, back up the database, installation registry, and the server files to be able to restore the server if the upgrade fails.
  - Upgrading the server in interactive mode
    To upgrade the server in interactive mode, start the installation of a newer version of BigFix Inventory on the same computer. In interactive mode, you upgrade the server through a wizard.
  - Upgrading the server in silent mode
    To upgrade the server in silent mode, start the installation of a newer version of BigFix Inventory on the same computer. Silent installation runs in the background.
  - Updating the server database schema
    BigFix Inventory server database schema gets updated when upgrading from one version to another.
  - Upgrading the scanner, tools and actions
    Upgrade BigFix Inventory scanner, tools, and actions as part of server upgrade process.
  - Restoring the server after a failed upgrade
    After a failed upgrade, you can restore the server to its original state by restoring the database, installation registry, and the server files from backups.
- Migrating BigFix Inventory

Restoring the server after a failed upgrade

After a failed upgrade, you can restore the server to its original state by restoring the database, installation registry, and the server files from backups.

Before you begin

If you did not back up the installation directory and the registry, you can install the new server and restore only the database. You can keep the data that is already in your database and avoid running the initial import.

Procedure

Stop the server.
Restore the database from a backup.

Restore the DB2 database.
Restore the SQL Server database.
Replace the installation registry with the backup registry. Copy the .com.zerog.registry.xml backup file to one of the following directories:

/var/
C:\Program Files\Zero G Registry\
If you installed the server as a non-root user, copy the backup file to $HOME/.
Replace the installation directory with the backup directory.
Start the server.