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

[#1]

Article Number

000039255

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: All
 

Issue

There 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.
 

Resolution

Once 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:

• If you use AFX and/or remote collection agents, regenerate and deploy certificates as described in RSA Knowledge Base Article 000038314 -- How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle. Alternatively download and deploy the AFX Server Archive as described in RSA Knowledge Base Article 000037993 -- How to download and install the AFX Server Archive in RSA Identity Governance & Lifecycle.
• Ensure the SON is correct (Admin > System > Server Nodes tab.)
• Ensure the outbound email URL is correct (Admin > Email > Settings.)