000039255 - Tips for restoring a Database to a different Server in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Aug 24, 2020Last modified by RSA Customer Support Employee on Aug 24, 2020
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000039255
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: All
 
IssueThere are times when you may want to restore a database backup to a different server from which the backup was taken. For example, you may want to restore a copy of your Production database to your DEV system to perform testing with your Production data. Or you may want to move your DEV data to your QA machine. Or your hardware may have failed and you have to restore your database to another system to continue functioning. Or you be dedicating a separate system for reporting or disaster recovery.

The purpose of this RSA Knowledge Base Article is to list additional tasks that may be required in addition to the actual import of the database.
 
ResolutionOnce a database has been imported to a new server, make sure the following additional tasks occur:

Before logging into the user interface:
  • Copy the encryption key files located on the original server in $AVEKSA_HOME/security and restore those files to $AVEKSA_HOME/security on the new server.
  • If the database is from a previous version/patch level, migrate the database using the AuthorizeMigration password in the Initialization screen as explained in the RSA Identity Governance & Lifecycle Installation Guide for your specific version.
  • Restore customizations (if any).

After logging into the user interface:

 

Attachments

    Outcomes