Backing up your current Tivoli Netcool Performance Manager environment

This section is included as a reminder that performing regular backups of the systems in your Tivoli® Netcool® Performance Manager environment is important.

Backup is especially important before a major change such as an upgrade procedure is performed on a system.

Backing up the database

It is recommended that you perform regular backups of the Tivoli Netcool Performance Manager Database, and it is recommended that you perform a cold backup of the Database before beginning an upgrade procedure. For information on Database backup and recovery, see the Database Administration.

Backing up the database

The Tivoli Netcool Performance Manager 1.4.3 database uses DB2 features that assist loading performance (for example, DB2 LOAD with the unrecoverable option.) The use of these features complicates the backup and recovery strategy. To reduce complexity and enhance reliability, procedures are developed to assist the user with backup and recovery strategy. These procedures must be considered as a set of recommendations, requirements, and sample code to assist the user in their environment. Many companies have well-defined procedures in place to perform backup of their databases. With this in mind, a backup procedure that meets IBM requirements with the maximum flexibility for the customer, is developed. In this section, the difference between required steps and sample steps are detailed. Database, and it is recommended that you perform a cold backup of the Database before beginning an upgrade procedure. For information on Database backup and recovery, see the Database Administration.

Backing Up DataChannel

It is recommended that you backup the DataChannel directories (/opt/proviso/datachannel, by default) on each host after the DataChannel components and processes have been shut down.

Backing Up DataLoad

It is recommended that you back up the DataLoad directories (/opt/dataload, by default) on each host before beginning an upgrade procedure.

Backing Up DataMart

While the upgrade procedure automatically backs up files that you may have changed, it is recommended that you backup the DataMart directories (/opt/datamart, by default) on each host before beginning an upgrade procedure.

Backing Up DataView

To back up DataView, do the following:

  1. As root, use the export command to extract the DataView content from the Dashboard Application Services Hub (DASH) deployment. 
    export.sh DASHLocation DASHUser DASHPassword

    For example:

    export.sh /opt/IBM/JazzSM/products/tnpm/dataview smadmin smadmin1
  2. Backup the <DASH_HOME>/products/tnpm/dataview directory using the preferred backup utility.