Server Recovery

  1. Ensure that the new BigFix server computer can be reached on the network using the same URL that is in the masthead file. (For example: OR
    Note: To avoid issues when the BigFix clients connect to the BigFix server before it is fully restored, ensure that the BigFix server is not available on the network until the recovery is complete.
  2. Remove all the installed BigFix components, including any plug-in. For more information about removing the BigFix components on Linux, see Removing the Product Components on Linux systems.
  3. Remove the following BigFix files and folders:
    Where "BES*" is a prefix followed by the name of a BigFix component, for example "BESClient".
  4. Restore the previously saved BFENT and BESREPOR as follows:
    su - db2inst1
    db2 restore db BFENT
    db2 restore db BESREPOR
    If saved with an absolute path, use the following command:
    su - db2inst1
    db2 restore db BFENT from /Absolute/Path/Of/Backup/Folder
    db2 restore db BESREPOR from /Absolute/Path/Of/Backup/Folder
  5. Restore only the previously saved folders and files:
  6. Remove the old password files:
  7. Copy the old configuration files in a temporary directory, as they might contain custom settings that you use, then delete them:
  8. If you have installed WebUI, remove the cert folder that contains the WebUI certificates:
  9. Download the same BigFix version and run the installation with option -reuseDb:
    ./ -reuseDb
    Install the BigFix server components using the masthead file and specifying the same path used in the original installation option.
  10. Manually add again the custom settings that you use by copying them from the old configuration files backed up in step 7 to the new configuration files:
    created when running the installation in step 9.