Backing up configuration and database files (SAP SQL Anywhere)

After the disaster recovery system is configured, you must back up the database and configuration files of the primary TrueSight Infrastructure Management Server.

This is critical to bring up the recovery TrueSight Infrastructure Management Server at the time of a disaster. You can do this after shutting down the primary TrueSight Infrastructure Management Server and copying the entire Infrastructure Management installation directory to the recovery TrueSight Infrastructure Management Server.

BMC recommends that you use a storage replication solution to back up the database and configuration files at regular intervals. This solution ensures consistency between the cell database and the TrueSight Infrastructure Management Server database even when the TrueSight Infrastructure Management Server is up and running. It also helps reduce the recovery time.

Backup frequency

The state of the recovery TrueSight Infrastructure Management Server depends on how recently you backed up your files. According to your organization's IT policies, you can decide whether to have daily, weekly, or monthly backups. BMC recommends that you create a backup of the files after any configuration changes are made to the server.

Files to back up

The following table list critical files and directories that must be backed up for a recovery of TrueSight Infrastructure Management Server to be successful.

Note

BMC recommends that you back up all of the following files at the same time to ensure that the files are synchronized.

File type

Files to back up

Configuration files

The configuration files include information about adapters and instances. Ensure that you back up the following files:

(Windows) Configuration files to backup
  • pw\monitors\monitors_
  • pw\pronto\usr_
  • pw\pronto\conf
  • pw\pronto\data\admin
  • pw\pronto\data\cell
  • pw\custom\conf
  • pw\server\etc
  • pw\server\etc\pncell_cellName
  • pw\server\log
  • pw\server\tmp
  • pw\server\var
  • pw\admin\etc\mccscommunication
(Linux) Configuration files to backup
  • pw/monitors/monitors_
  • pw/pronto/usr_
  • pw/pronto/conf
  • pw/pronto/data/admin
  • pw/pronto/data/cell
  • pw/custom/conf
  • pw/server/etc
  • pw/server/etc/pncell_cellName
  • pw/server/log
  • pw/server/tmp
  • pw/server/var
  • pw/admin/etc/mccscommunication

In the Calbro Services example, cellName refers to amsterdam. If you change the default name during TrueSight Infrastructure Management Server installation, cellName refers to the name that you specified.

KB files

Ensure that you back up all of the KB files. The files are located in the following directories:

  • (Windows) pw\server\etc\pncell_cellName\kb
  • (Linux) pw/server/etc/pncell_cellName/kb

For the Calbro Services example, cellName refers to amsterdam. If you changed the default name during TrueSight Infrastructure Management Server installation, cellName refers to the name that you specified.

Cell database files

Ensure that you back up the mcdb and xact cell database files. The files are located in the following directories:

  • (Windows) pw\server\var\pncell_cellName
  • (Linux) pw/server/var/pncell_cellName

For the Calbro Services example, cellName refers to amsterdam. If you changed the default name during TrueSight Infrastructure Management Server installation, cellName refers to the name that you specified.

Database files

Ensure that you back up the pronto.log and storm_hostName.db database files. The files are located in the following directories:

  • (Windows) pw\sybase
  • (Linux) pw/sybase

For the Calbro Services example, hostName refers to amsterdam.

Note

Use the pw database archive command to back up the database files. For more information about the backup procedure, see pw database archive.