User Tools

Site Tools


deploy:bigfix_restore

BigFix Server Recovery

How to perform a server recovery.

  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: http://192.168.10.32:52311/cgi-bin/bfgather.exe/actionsite OR http://bigfixserver.company.com:52311/cgi-bin/bfgather.exe/actionsite).

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.

Step 1

Stop BigFix server

/etc/init.d/LMTserver stop
/etc/init.d/besfilldb stop
/etc/init.d/besgatherdb stop
/etc/init.d/besserver stop
/etc/init.d/beswebreports stop
/etc/init.d/besclient stop

Step 2: Remove old files and folders

Remove all the installed BigFix components, including any plug-in.

rm -rf /etc/opt/BES*
rm -rf /opt/BES*
rm -rf /tmp/BES
rm -rf /var/log/BES*
rm -rf /var/opt/BES*

Step 3: Restore DBs

Where “BES*” is a prefix followed by the name of a BigFix component, for example “BESClient”.

Restore the previously saved BFENT, BESREPOR, and TEMADB as follows:

su - db2inst1
db2 restore db BFENT
db2 restore db BESREPOR
db2 restore db TEMADB

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
db2 restore db TEMADB from /Absolute/Path/Of/Backup/Folder

Step 4: Restore files and folders

Restore only the previously saved folders and files:

/var/opt/BESClient
/var/opt/BESCommon
/var/opt/BESServer
/var/opt/BESWebReportsServer
/var/opt/BESWebUI

Step 5: Remove files

Remove the old password files:

/var/opt/BESClient/besclient.obf 
/var/opt/BESServer/besserver.obf 
/var/opt/BESWebReportsServer/beswebreports.obf

Copy the old configuration files in a temporary directory, as they might contain custom settings that you use, then delete them:

/var/opt/BESClient/besclient.config
/var/opt/BESServer/besserver.config
/var/opt/BESWebReportsServer/beswebreports.config
/var/opt/BESWebUI/beswebuiservice.config

If you have installed WebUI, remove the cert folder that contains the WebUI certificates:

/var/opt/BESWebUI/cert

Download the same BigFix version and run the installation with option -reuseDb:

  ./install.sh -reuseDb
  Install the BigFix server components using the masthead file and specifying the same path used in the original installation option.
      If migrating the Primary/Master server, on the Select Database Replication page of the server installer, select “Single or Master Database”, and proceed through the installer screens as usual.
      If migrating the Secondary/Replica server, on the Select Database Replication page of the server installer, select “Replicated Database”, and proceed through the installer screens as usual.
  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:
  /var/opt/BESClient/besclient.config
  /var/opt/BESServer/besserver.config
  /var/opt/BESWebReportsServer/beswebreports.config
  /var/opt/BESWebUI/beswebuiservice.config
  created by the installation at Step 9.
  To avoid the duplication of the server computer entry on the BigFix Console, run the steps for Procedure to keep the client identity.
  Reinstall the UAImporter, BES Server Plugin Service, and any plugins or components that are currently installed on the original BigFix server by re-deploying the appropriate Fixlets.
deploy/bigfix_restore.txt · Last modified: 2023/12/11 14:57 by manu