IBM Performance Management

Backing up and restoring for disaster recovery

For disaster recovery, run the backup.sh script to back up the Performance Management server components and their configuration on the source server and then run the restore.sh script to restore these components to the target server.

About this task

All Performance Management server components are backed up and restored with the backup.sh and restore.sh scripts. The backup.sh script completes an online backup of the DB2® databases. If the database is not configured for online backup, an offline backup is completed.
Tip: When you run the backup.sh or restore.sh scripts, if you provide a custom password that has non-alphanumeric characters, you must surround the password with single quotation marks. For example, /opt/custom/ccm/backup.sh -p 'Z!@12ws*'
When you install the Performance Management server on the target server, you must meet the following requirements:
  • Install the same offerings on the target server as the source server.
  • Use the same installation path on the target server as the source server.
  • Use the same passwords for the following user IDs on the target server as the source server:
    • apmadmin
    • smadmin
    • MongoDB user IDs
    For more information, see Default users and passwords.
  • Use the same type of DB2 database (either local or remote) on the target server as the source server.

Procedure

In the following steps when you are setting the user ID passwords either at server installation time or after the server is up and running, ensure that these passwords are the same on the target server as the source server.

  1. Back up all the server components and their configuration by completing the following steps:
    1. Run the install_dir/ccm/backup.sh script on the source server to generate the backup file. To list all available parameters for this script, run it with the -h option.
      • If you want to, you can specify a name for the backup file and the administrator's user ID and password. By default, the script creates a backup TAR file in the install_dir/backups directory.
      • If your system includes an external DB2 database, copy the install_dir/ccm/backup.sh script to the computer where DB2 is installed and run the backup.sh script (only DB2 is backed up).
    2. Transfer the backup file to the target server.
    3. Shut down the source server.
    4. Change the IP address and host name on the target server to match the source server.
    5. Install the same version of the Performance Management server on the target server as the source server. If a Performance Management server interim fix is installed on the source server, you must install the same Performance Management server interim fix on the target server. Also, if you installed a DB2 fix pack on the DB2 server that is used by the Performance Management source server, then you must apply the same DB2 fix pack on the database server that is used by the Performance Management target server before you complete the restore.
  2. As user root, complete one of the following steps (depending on whether your DB2 database is local or remote) to restore the configuration and data. To list all available parameters for the restore.sh script, run it with the -h option. When you are running this script, you can optionally specify the administrator's user ID and password.
    • If the DB2 database is local, run the install_dir/ccm/restore.sh -f backup_file script on the target server. backup_file is a path to the backup file created by the backup.sh script.
    • If the DB2 database is remote, follow these instructions:
      If you are not reinstalling the Performance Management server, complete the following steps on the target server:
      1. Stop all the server components by running the apm stop_all command.
      2. Restore the Performance Management server configuration and data by running the install_dir/ccm/restore.sh -f backup_file script on the target server.
      If you are reinstalling the Performance Management server, complete the following steps:
      1. On the target server, stop all the server components by running the apm stop_all command.
      2. To restore the external DB2 databases, copy the install_dir/ccm/restore.sh script to the system where DB2 is installed and run the ./restore.sh -f Db2_backup_file script. Db2_backup_file is the backup file that is created by the backup.sh script on the system where DB2 is installed.
      3. On the target server, restore the Performance Management server configuration and data by running the install_dir/ccm/restore.sh -f backup_file script.

Results

The Performance Management server backup and restore procedure is complete. You can now access data for your agents and other components from the target server.

What to do next

  • If you used a different server IP address and host name in 1.d, complete the steps in Changing the server IP address and host name to update the IP address and host name that are used by the target Performance Management server components and by your managed resources. Also, if a different URL is needed to log in, notify your Performance Management console users.
  • If you enabled single sign-on between the Performance Management server and Tivoli® Common Reporting, you must enable single sign-on again after you restore the Performance Management server.
    1. Disable OpenID connect (OIDC) authorization. For more information, see Disabling OpenID Connect authentication for the Performance Management console.
    2. Complete steps 8 and 9 in Enabling single sign-on between IBM Performance Management and Tivoli Common Reporting to update the server.xml file and restart the Performance Management console.