Before upgrading
Perform these steps before upgrading the BigFix components:
- Close all BigFix consoles.
- Back up your BigFix server and database.
- Back up your
license.pvk
,license.crt
, andmasthead.afxm
to a separate location on the BigFix server or to a USB key. - If your server is configured in a DSA environment, increase the replication interval to prevent the replication from failing repeatedly during the upgrade. For additional information, see Changing the replication interval on Linux systems.
- Upgrade the BigFix components
according to the following order:
- Servers and consoles (console and server must have the same version and must be upgraded at the same time.
- Relays
- Clients
Note: Existing BigFix proxy configurations are automatically migrated to the V9.2 proxy configuration settings and behavior. For more information about BigFix V9.2 proxy configuration settings, see Setting up a proxy connection. - For DSA servers, upgrade first one DSA server to ensure the upgrade is successful and then the other DSA servers.
Note:
- For large deployments, the server upgrade might take several minutes.
- After an upgrade your deployment might be slow because the upgrade downtime can create a backlog of client reports, and it can take several hours for the IBM BigFix server to process this backlog after the upgrade has completed.