Backup and restore on two different Authentication Manager servers
Please note:
1. To restore the data on a different machine, you must add a flag "-D" or "--transfer" in the command when backup and restore.
2. Besides the database server service, the database listener and database instance service must also be started when restoring the database.
How to Move RSA Authentication Manager 7.1 SP4 data to a new system:
- On the new system:
1) Install clean RSA Authentication Manager 7.1 SP4 full installation kit - installed using the same administrative accounts and master password as the previous production system to ensure the encrypted IMS data backup restores correctly.
2) You will need to add the Radius server through the Operations Console just as you did for the existing AM 7.1 configurations before restoring the database.
On the existing AM 7.1 system:
1) Take a backup on the current Appliance system which runs AM 7.1sp 4:
<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->
<!--[if !supportLists]-->? <!--[endif]-->Open a CMD on the Primary, run:
<!--[if !supportLists]-->? <!--[endif]-->cd c:\Program Files\RSA Security\RSA Authentication Manager\utils
<!--[if !supportLists]-->? <!--[endif]-->rsautil manage-backups -a export -D ?f c:\backup.dmp
This will create two files in the /tmp directory, one named backup.dmp, the other named backup.secrets.
2) Archive/zip-up the Radius directory from here:
<!--[if !supportLists]-->? <!--[endif]-->cd c:\Program Files\RSA Security\RSA Authentication Manager\radius
3) Copy these files (the two dmp files and the radius.zip) over to the new system.
4) You can take this system off the network now to avoid IP/hostname conflicts with the new AM 7.1 system.
<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->
On the new system:
1. Configure the RADIUS Server
2. Stop all Authentication Manager Services:
3. Then start the database listener, database instance, and database server services (needed for the db import):
4. Remove the primary metadata:
<!--[if !supportLists]-->? <!--[endif]-->Open a CMD on the Primary, run:
<!--[if !supportLists]-->? <!--[endif]-->cd c:\Program Files\RSA Security\RSA Authentication Manager\utils
<!--[if !supportLists]-->? <!--[endif]--> rsautil setup-replication -a remove-primary
5. Import the database:
<!--[if !supportLists]-->? <!--[endif]-->rsautil manage-backups -a import -D -f c:\backup.dmp
6. Reset the primary metadata:
<!--[if !supportLists]-->? <!--[endif]-->rsautil setup-replication -a set-primary
7. Copy the radius.zip file over to /RSA Security/RSA Authentication Manager
(It should then list out as /RSA Security/RSA Authentication Manager/radius/Service)
8. After the import completes and the radius folder is in place, start all the other RSA services
9. Login to the Security console and verify if users are there. Test authentication out.
Related Articles
Failed RSA SecurID Authenticate tokencode authentication attempt to RSA SecurID Authentication Manager causes two failures… 34Number of Views How to collect data from an RSA Authentication Agent 7.x for Windows for troubleshooting 247Number of Views RSA Identity Governance and Lifecycle MigrationReports.zip fails to install Migration Reports with ORA-04063: package body… 152Number of Views In RSA Identity Governance & Lifecycle, duplicate entries are created when a user switches between two Identity Data Colle… 71Number of Views RSA Identity Governance & Lifecycle authentication fails if the authentication sources uses Aveksa Data Collector (ADC) an… 220Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme AFX Server and Remote Collection Agents fail to start after updating Java to version 1.8u241 (1.8.0_241) / 1.7u251 (1.7.0_… Upgrade Internal Authentication Manager Certificates to SHA-256 RSA Authentication Manager 8.9 Setup and Configuration Guide Upgrading the Internal SecurID Authentication Manager 8.6 Certificates to SHA-256