Migrate Threat Analytics for PAM from version 2.2.3r1 to version 2.3

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

How can we migrate the current Threat Analytics (TA) for PAM version 2.2.3r1 data into the new TA version 2.3?

Environment

Release : 2.3

Component : Threat Analytics for PAM

Resolution

We have the following procedure to perform a TA OVA-to-OVA Upgrade.

1. Create and download a backup in the old system
   a. Log in to the Admin App (port 3000 on the appliance)
   b. Stop the Threat Analytics service
         i. Click the Threat Analytics Engine link
        ii. Click the Stop button
       iii. Wait for the page to refresh, and confirm that status bar has turned from Green (Running) to Yellow (Stopped)
   c. Download a backup file
         i. Click the Backups link in the header
        ii. Click the Create A New Backup button
       iii. Refresh the page until you see a new backup in the table at the bottom. It will be called interlock_YYYYMMDDHHMM.sql.gz, where YYYYMMDDHHMM is the current date and time.
       iv. Click the Download button in that entry to download the backup

2. Import and migrate the database in the new VM
   a. Start the new TAP 2.3 VM and configure the networking and date
   b. Open the Administrative Application on the new appliance (port 3000)
   c. Stop the Threat Analytics service
        i. Click the Threat Analytics Engine link
       ii. Click the Stop button
      iii. Wait for the page to refresh, and confirm that status bar has turned from Green (Running) to Yellow (Stopped)
   d. Run the following task:

      db:drop

   e. Once the db:drop task is complete, run the following task:

      db:create

   f. Restore the backup
        i. Click the Backups link in the header
       ii. Under Restore Backup, choose the backup file you made in Step 1
      iii. Click the Restore button
      iv. Refresh the page until the text below the Restore Backup section reads “Last restore completed…”

   g. Run the following task to migrate the database:

      db:migrate

   h. Return to the homepage of the Administrative Application. Click the Restart button for the Threat Analytics Engine. Reload the page until the badge reads “active”.
   i. Log into Threat Analytics on the new VM. Verify that the data migrated successfully.

3. Update configuration
   a. Log in to PAM and update the hostname for the CA Threat Analytics integration
      See

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/privileged-access-manager/4-1/integrating/integrate-with-ca-threat-analytics/deploy-ca-threat-analytics-server.html#concept.dita_e49c142d04a41299ff74f32a25743aa764754481_ConfigureCAThreatAnalytics

   b. Re-configure SAML for Threat Analytics
      See

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/privileged-access-manager/4-1/integrating/integrate-with-ca-threat-analytics/set-up-saml-punch-through-authentication-optional.html