Verifying restore results

Ensure that your BigFix Server has been restored.

Perform the following steps:

  1. Verify that all services are started.
  2. Log in to the BigFix console and verify that the login works and that the database information was restored. In case of a login failure, see https://hclpnpsupport.hcltech.com/csm?id=kb_article&sysparm_article=KB0023746.
  3. Use the DB client to connect to BFENT and examine the DBINFO and REPLICATION_SERVERS tables. Compare the current values to the values noted running the Server Backup procedure.
  4. Verify that the new BigFix Server is able to connect to the database. Check all the Server logs for error messages on connecting to the database.
  5. Reconfigure any appropriate BigFix Server settings.
  6. If leveraging a DNS name/alias within the masthead, perform a DNS switch for the DNS name so that the alias now points to the new BigFix Server. Wait for the DNS switch to propagate (this may take some time depending on your DNS services/infrastructure).
  7. Ensure that the BigFix clients and BigFix relays connect to the server when it is available and report data to it. Full recovery with all agents reporting might take from a few minutes to many hours (depending on the size of the deployment and how long the server was unavailable). At least some agents should be reporting updated information within an hour.
  8. After verifying that some agents are reporting to the server, send a blank action: Tools > Take Custom Action to all computers. The blank action does not make any changes to the agent computers, but the agents report that they received the blank action.
  9. Log in to the web reports and ensure that the data was restored.
    Note: If a remote datasource is defined in the Web Reports configuration, Web Reports connects to the datasource only after you re-enter the datasource credentials in the Web Reports Administration > Datasource Settings > Edit page.