Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Backup and restore of the BladeLogic environment

This topic was edited by a BMC Contributor and has not been approved.  More information.

BMC recommends that you set up a backup policy for the BMC BladeLogic 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 BMC BladeLogic Server Automation environment.

ComponentBackup mechanism
DatabaseBack up the BladeLogic 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:

  • <install dir>/NSH/br/deployments/bladelogic.keystore
  • <install dir>/NSH/share/sensors
  • <install dir>/NSH/scripts
  • If Active Dirctory or Domain logon is enabled:
    • <install dir>/NSH/br/blappserv_krb5.conf
    • <install_dir>/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 windows
    • UNIX: /opt/bmc/bladelogic/NSH/br/.bladelogic

To back up the Application Server configuration, use one of the following methods:

  • File-based: Back up the configuration files. These files are stored in the <install dir>/NSH/br/deployments directory.  Note that these files are unique for each Application Server host and contain host name specific settings.
  • Script-based: Copy the configuration to a file and later restore it by periodically running a script. The advantage of this approach is that the configuration can be restored to a different physical server.
    Your script might run the following blasadmin command. In this example, the source file is stored in /tmp. You can store this file in any location other than the <install dir>/NSH directory.
    blasadmin -s <deployment name> show all > /tmp/<deployment name>.txt

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 BMC BladeLogic Server Automation environment.

ComponentRestore mechanism
DatabaseRestore the BladeLogic 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, use one of the following methods:
    • File-based: Restore the <install dir>/NSH/br/deployments files and directories to their original locations, overwriting the current files.
    • Script-based: Run a script to create and configure the various Application Server deployments based on the backed-up configurations.
  • After completing the restore process, start up the Application Server services.
Was this page helpful? Yes No Submitting... Thank you

Comments