Backup and restore of the TrueSight Server Automation environment

BMC recommends that you set up a backup policy for the TrueSight Server Automation environment to ensure that your data is saved if your environment suffers corruption or failure. Each component of the environment has a specific backup mechanism.

Backup

The following table summarizes the backup mechanisms recommended for the various components in the TrueSight Server Automation environment.

Component

Backup mechanism

Database

Back up the TrueSight Server Automation Schema using your preferred database backup software.

File server

Use your preferred file backup software to back up the entire directory shown in the blasadmin show file location output.

Application Server

Back up the following Application Server files:

  • <installDirectory>/NSH/br/deployments/bladelogic.keystore
  • <installDirectory>/NSH/br/deployments/global.properties
  • <installDirectory>/NSH/br/deployments/db.keystore
  • <installDirectory>/NSH/br/deployments/dbkeystorepw.txt
  • <installDirectory>/NSH/share/sensors
  • <installDirectory>/NSH/scripts
  • If Active Directory or Domain logon is enabled:
    • <installDirectory>/NSH/br/blappserv_krb5.conf
    • <installDirectory>/NSH/br/blappserv_login.conf
  • Any custom files not stored in the file server location
  • If you are using certificate authentication for the connection between the Application Server and the RSCD Agents (whether on UNIX or Windows), back up the id.pem file on the Application Server. The id.pem file can be found in the following location:
    • Windows: %WINDIR%\rsc\certs\SYSTEM, where %WINDIR% is typically C:\Windows
    • UNIX: /opt/bmc/bladelogic/NSH/br/.bladelogic
  • If you are using CA-signed, server side certificate authentication for the connection between the Application Server and the RSCD Agents (whether on UNIX or Windows), back up the rscd.cabundle.pem file on the Application Server. This file typically resides in the following directory:
    • UNIX: <installDirectory>/NSH/br/deployments
    • Windows: <installDirectory>\NSH\br\deployments


The Application Server deployment information is stored in the database, therefore there is no need to preserve the individual deployment directories (NSH/br/deployments)

Smart Hub

Back up the files from these locations:

  • <smarthub_installation_location>/data/
  • <smarthub_installation_location>/certs

For details, see Migrating-the-Smart-Hub-and-Redis-Server-data.

Smart Hub Gateway

Back up the files from these locations:

  • <smarthub_Gateway_installation_location>/conf/applicaton.properties
  • <smarthub_Gateway_installation_location>/conf/infraId.txt
  • <smarthub_Gateway_installation_location>/conf/cert/*

For details, see Migrating-the-Smart-Hub-and-Redis-Server-data.

Note

Ensure that your database and file server backups are correlated.

Restore

The following table summarizes the restore mechanisms recommended for the various components in the TrueSight Server Automation environment.

Component

Restore mechanism

Database

Restore the TrueSight Server Automation schema using your preferred database backup software.

File server

Use your preferred file backup software to restore the file server contents.

Application Server

Use the following guidelines:

  • Install the same version of the Application Server in the same directory location.
  • Do not run the blappconf post-installation wizard. 
  • Restore the backed-up files to their original locations.
  • To restore the Application Server configuration
    • Run a single blasadmin command against template on each application server to trigger the pull of the application server configuration from the database
      • blasadmin -s _template set Database DriverClassoracle.jdbc.driver.OracleDriver (or the appropriate driver class)

  • Start the blappserv service and the existing deployments will be pulled from the database

    The hostname of the restored system must exactly match that of the old system or the application server deployments will not be pulled from the database.

Smart Hub

Restore the files from the backed up locations. For details, see Migrating-the-Smart-Hub-and-Redis-Server-data.

Smart Hub Gateway

Restore the files from the backed up locations. For details, see Migrating-the-Smart-Hub-and-Redis-Server-data.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*