Restore Performance Center

Restore an existing backup of npc.
capm370
Restore an existing backup of
Performance Center
.
Restore the Database After a Reinstallation
Restore the
Performance Center
database from a backup archive after you reinstall the software. Restoring the database from a backup preserves data continuity and enables most historical reporting after a failure occurs.
Database restoration is required only if a failure occurs. Take the cleanup steps that are described in Clean Up After a Failed Installation before you attempt the installation again. Then, take the steps in this procedure.
For upgrade failure situations, follow the steps in Recover from an Upgrade Failure.
Follow these steps:
  1. Log in to the server as 'root', or use the 'sudo' account that you configured for the installation.
  2. Stop all the
    Performance Center
    services using the following commands:
    service caperfcenter_eventmanager stop
    service caperfcenter_devicemanager stop
    service caperfcenter_sso stop
    service caperfcenter_console stop
  3. Change to the directory where you saved the backup archive:
    cd
    backup_Directory
  4. Uncompress the database backup archives for
    Performance Center
    and Event Manager by executing the following commands:
    tar zxvf netqosportal.tgz
    tar zxvf em.tgz
  5. Import the uncompressed
    Performance Center
    backup file:
    mysql netqosportal -u root -p
    password
    -e 'source $backupDir/netqosportal.sql'
  6. Import the uncompressed Event Manager backup file:
    mysql em -u root -p
    password
    -e 'source $backupDir/em.sql'
  7. Start the
    Performance Center
    services on the new system as follows:
    1. Start the SSO service:
      service caperfcenter_sso start
    2. Wait one minute, then start the event manager and device manager:
      service caperfcenter_eventmanager start
      service caperfcenter_devicemanager start
    3. Wait one minute, then start the console service:
      service caperfcenter_console start
  8. Delete the uncompressed archive files to save space:
    rm netqosportal.sql
    rm em.sql
  9. Log in to
    Performance Center
    as an administrator.
  10. Verify that your configuration data appears in the Admin pages.
Recover from an Upgrade Failure
Follow these steps to restore the
Performance Center
database and verify the database schema version. If the schema version matches the current product version, try the upgrade again. If not, see
Recover from an Upgrade Failure with an Error
for the steps to update the schema version.
Database restoration is required after an upgrade only if a failure occurs. Take the cleanup steps that are described in
Clean Up After a Failed Installation
before you attempt the upgrade again. Then, take the steps in this procedure.
Follow these steps:
  1. Log in to the server as 'root', or use the 'sudo' account that you configured for the installation.
  2. Stop all the
    Performance Center
    services, using the following commands:
    service caperfcenter_eventmanager stop
    service caperfcenter_devicemanager stop
    service caperfcenter_sso stop
    service caperfcenter_console stop
  3. Change to the directory where you saved the backup archive:
    cd
    backup_Directory
  4. Uncompress the database backup archives for
    Performance Center
    and Event Manager by executing the following commands:
    tar zxvf netqosportal.tgz
    tar zxvf em.tgz
  5. Import the uncompressed
    Performance Center
    backup file:
    If you leave out the optional password syntax from the following command, you are prompted for the password.
    mysql netqosportal -u root -p
    password
    -e 'source $backupDir/netqosportal.sql'
  6. Import the uncompressed Event Manager backup file:
    mysql em -u root -p
    password
    -e 'source $backupDir/em.sql'
  7. Change to the following installation directory:
    cd /opt/CA/PerformanceCenter/Tools/bin
  8. Run the following command to verify the database version:
    mysql -P3306 -D netqosportal -u root -p
    password
    mysql> select InstallDate, version, dbschemaversion from revision_info order by InstallDate asc;
    The output lists installation dates and versions of the software and database schema.
    If the database version does not match the current product version, follow the steps in
    Recover from an Upgrade Failure with an Error
    .
Recover from an Upgrade Failure with an Error
If an error occurs during an upgrade of the
Performance Center
software, restore the database and update the schema. See
Recover from an Upgrade Failure
for the steps to restore the database and verify the database schema version. If the schema version does not match the current product version, update the schema version.
Follow these steps:
  1. Upgrade the database schema. From the Tools/bin directory, run the npcshell database utility to upgrade the schema to the current version:
    ./npcshell.sh upgradedb
  2. Run the following commands to import database translation files:
    /opt/CA/jre/bin/java -jar /opt/CA/PerformanceCenter/SQL/seedlu/bin/seedlu.jar -resfile "/opt/CA/PerformanceCenter/SQL/messages_en_US.properties" -ctrlfile "/opt/CA/PerformanceCenter/SQL/control.sdlctrl" -connection "jdbc:mysql://localhost:3306/netqosportal?useUnicode=true&characterEncoding=UTF-8" -user netqos -pwd
    password
    -lang en-US
    /opt/CA/jre/bin/java -jar /opt/CA/PerformanceCenter/SQL/seedlu/bin/seedlu.jar -resfile "/opt/CA/PerformanceCenter/SQL/messages_zh_CN.properties" -ctrlfile "/opt/CA/PerformanceCenter/SQL/control.sdlctrl" -connection "jdbc:mysql://localhost:3306/netqosportal?useUnicode=true&characterEncoding=UTF-8" -user netqos -pwd
    password
    -lang zh-CN
    /opt/CA/jre/bin/java -jar /opt/CA/PerformanceCenter/SQL/seedlu/bin/seedlu.jar -resfile "/opt/CA/PerformanceCenter/SQL/messages_zh_TW.properties" -ctrlfile "/opt/CA/PerformanceCenter/SQL/control.sdlctrl" -connection "jdbc:mysql://localhost:3306/netqosportal?useUnicode=true&characterEncoding=UTF-8" -user netqos -pwd
    password
    -lang zh-TW
    /opt/CA/jre/bin/java -jar /opt/CA/PerformanceCenter/SQL/seedlu/bin/seedlu.jar -resfile "/opt/CA/PerformanceCenter/SQL/messages_fr_FR.properties" -ctrlfile "/opt/CA/PerformanceCenter/SQL/control.sdlctrl" -connection "jdbc:mysql://localhost:3306/netqosportal?useUnicode=true&characterEncoding=UTF-8" -user netqos -pwd
    password
    -lang fr-FR
    /opt/CA/jre/bin/java -jar /opt/CA/PerformanceCenter/SQL/seedlu/bin/seedlu.jar -resfile "/opt/CA/PerformanceCenter/SQL/messages_ja_JP.properties" -ctrlfile "/opt/CA/PerformanceCenter/SQL/control.sdlctrl" -connection "jdbc:mysql://localhost:3306/netqosportal?useUnicode=true&characterEncoding=UTF-8" -user netqos -pwd
    password
    -lang ja-JP
    Replace the '
    password
    ' variable with the password.
  3. Update the information that
    Performance Center
    uses to display administration pages and views. Run the following commands:
    • CA Infrastructure Management Administration Pages:
      ./npcshell.sh dbmigrate -package com.ca.im.plugin.pc -path ../../SQL/plugins/pc/
    • Event-Related Views:
      ./npcshell.sh dbmigrate -package com.ca.im.plugin.em -path ../../SQL/plugins/eventmanager/
    • Data Aggregator Administration Pages and Views:
      ./npcshell.sh dbmigrate -package com.ca.im.plugin.da -path ../../SQL/plugins/polaris/
  4. Run the following command again to verify the database version after you have upgraded it:
    mysql -P3306 -D netqosportal -u root -p
    password
    mysql> select InstallDate, version, dbschemaversion from revision_info order by InstallDate asc;
  5. Start all the
    Performance Center
    services:
    service caperfcenter_eventmanager start
    service caperfcenter_devicemanager start
    service caperfcenter_sso start
    service caperfcenter_console start
  6. Delete the uncompressed archive files to save space:
    rm netqosportal.sql rm em.sql
  7. Log in to
    Performance Center
    as an administrator.
  8. Verify that your configuration data appears in Admin pages.
Restore Single Sign-On Settings
If your
Performance Center
deployment uses single sign-on, restore the configuration settings.
Restore the following files:
  • /opt/CA/CA/PerformanceCenter/sso/start.ini
  • /opt/CA/CA/PerformanceCenter/PC/start.ini
Restore the follow directories:
  • /opt/CA/CA/PerformanceCenter/sso/webapps/sso/configuration
  • /opt/CA/CA/PerformanceCenter/sso/etc
  • /opt/CA/CA/PerformanceCenter/sso/conf
  • /opt/CA/CA/PerformanceCenter/PC/etc
  • /opt/CA/CA/PerformanceCenter/PC/conf
If you have enabled SSL, restore the following files:
  • /opt/CA/CA/PerformanceCenter/sso/start.d/ssl.ini
  • /opt/CA/CA/PerformanceCenter/PC/start.d/ssl.ini
Restore Custom Settings
If your deployment includes custom OpenAPI applications, restore the application folder:
  • /opt/CA/PerformanceCenter/PC/webapps/pc/apps
If you use custom logos for your themes, restore the following files:
  • /opt/CA/PerformanceCenter/PC/webapps/pc/css/CA-Blue/images/customLogo
  • /opt/CA/PerformanceCenter/PC/webapps/pc/css/CA-Gray/images/customLogo
Restore Reports
Full PDF reports are temporarily saved for download.
Restore the following directory:
  • /opt/CA/PerformanceCenter/DM/repository
Restore Script Notification Actions
If you have script notification actions, restore the following directory:
  • /opt/CA/PerformanceCenter/NotificationScripts
Update the Data Aggregator and Event Manager Data Sources
If the new
Performance Center
hostname is different from the original
Performance Center
host, update the the Data Aggregator and Event Manager data sources.
Performance Center
Disaster Recovery Script
Location:
/opt/CA/PerformanceCenter/Tools/bin/update_pc_da_database_references.sh
On the
Performance Center
host in the recovery system, update the bold sections of the script to match your system:
...
##################################################################
# UPDATE THE FOLLOWING PC/DA VARIABLES TO REFLECT NEW ENVIRONMENT
##################################################################
NEW_PC_IP_ADDRESS="
<Recovery/New PC IP Address>
"
NEW_PC_HOSTNAME="
<Recovery/New PC Hostname>
"
NEW_PC_EVENT_PRODUCER_PORT=
8181
NEW_PC_EVENT_PRODUCER_PROTOCOL="
http
" # change to "https" if using SSL
NEW_DA_IP_ADDRESS="
<Recovery/New DA IP Address>
"
NEW_DA_HOSTNAME="
<Recovery/New DA Hostname>
"
NEW_DA_PORT_NUMBER=
8581
...
Start
Performance Center
Follow these steps:
  1. Restore the
    Performance Center
    backups.
  2. Run the
    Performance Center
    disaster recovery script:
    /opt/CA/PerformanceCenter/Tools/bin/
    your_update_pc_da_database_references.sh
  3. Start the SSO service:
    service caperfcenter_sso start
  4. Wait one minute, then start the event manager and device manager:
    service caperfcenter_eventmanager start
    service caperfcenter_devicemanager start
  5. Wait one minute, then start the console service:
    service caperfcenter_console start
Resynchronize the Event Manager Database
The recommended backup and restore procedures include an instruction to back up the Event Manager database.
If you neglect this step, problems can occur when the Event Manager tries to synchronize with
Performance Center
. The synchronization can fail because
Performance Center
has outdated Event Manager information. The newly installed Event Manager has the new information.
If this problem occurs, resynchronize these two databases.
Since this procedure does not include a step to restore the Event Manager database, notifications are not preserved, and must be recreated. Otherwise, the Event Manager runs normally.
Follow these steps:
  1. Log in as a user with the Administrator role.
  2. Navigate to the Manage Data Sources page.
    The current list of registered data sources appears on the Manage Data Sources.
  3. Select the data source that you want to remove (unregister).
  4. Click Remove, and then click Yes to confirm the deletion.
    The data source is removed from the list.
  5. Remove all properties that are related to
    Performance Center
    from the em.general database table using the following command:
    DELETE from em.general where Attribute LIKE 'NPC.%';
  6. Restart Event Manager using the following command:
    service caperfcenter_eventmanager restart
  7. Return to the Manage Data Sources page.
  8. Register the Event Manager data source.