Unable to restore a backup data more than once when a restore destination is not same Authentication Manager of the backup data in RSA Authentication Manager Virtual Appliance.

[#1]

Article Number

000037871

Applies To

RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.3.0

Issue

• When restoring a backup to an RSA Authentication Manager primary that has already restored the same Authentication Manager backup, the following error occurs:

Starting RADIUS clean-up..
Stopping RADIUS server

Setting RADIUS to primary...
Successfully set RADIUS to primary.
Configure RADIUS...
Failed to configure RADIUS.
Failed to configure RADIUS.
An error occurred that prevented the system from being restored.  THe backup file that you selected to restore your system is \\192.168.10.64
\c$\backup\201907241443.RSAbackup.
Failed to clean-up RADIUS data.
Please call customer support.  For error details, check the "Advanced Status VIew.'
 

Error:
Failed to clean-up RADIUS
 

Image description

The /opt/rsa/am/server/logs/imsOCTrace.log will show the following error:

...
@@@2019-07-24 17:07:03,692, [RestoreBackup], (CLUAuditLogFactory.java:169), trace.com.rsa.tools.common.CLUAuditLogFactory, ERROR, naka-am830-01.cs-rsa.local,,,,Error initializing CLU database logging org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SQLErrorHelper' defined in class path resource [applicationContext-db-logging.xml]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Initialization of DAO failed; nested exception is java.lang.RuntimeException: org.postgresql.util.PSQLException: The connection attempt failed. 

...

Cause

RSA Authentication Manager checks whether the backup source and restore destination are the same Authentication Manager server or not. If the restore function detects that the backup source and restore destination are the same Authentication Manager server, it restores all of the system data.

In this case, the Authentication Manager destination server was already restored with the same of Authentication Manager backup; which is why this restoration fails.

Note: You can see the difference of restoring system data in the Advanced Status View, as shown here:

When the backup and restore destination is the same Authentication Manager

When the backup and restore destination is not same Authentication Manager

... Starting System restore.. Restoring system files from staging file [Directory  of staging files] Successful copied resolv.conf Successful copied HOSTNAME Successful copied routes Successful copied hosts Successful copied Guid.MetaData.properties Successful copied Guid.Values.properties Successful copied ifcfg-eth0 Restoring SSL server certificates Restoring SSL server certificates completed Starting RADIUS clean-up.. Stopping RADIUS server ...

... Starting System restore.. Restoring system files from staging file [Directory  of staging files] Successful copied resolv.conf Successful copied hosts Successful copied Guid.MetaData.properties Successful copied Guid.Values.properties Renaming properties files to new instance. Restoring SSL server certificates Restoring SSL server certificates completed Starting RADIUS clean-up.. Stopping RADIUS server ...

Resolution

If you would like to restore backup data to the same Authentication Manager one more time, there are two ways to complete the task.  Either:

• Change the Authentication Manager server hostname of the restore destination temporarily:

1. Login to the Operations Console of the primary and go to Administration > Network > Appliance Network Settings.
2. Change the Fully Qualified Domain Name to other name which you want to restore.
3. Try to restore the backup data.

• Setup a new virtual appliance

1.  Setup a new virtual appliance as restore destination.
2.  Try to restore the backup data.

Notes

Use case:

1. Get backup data of Authentication Manager.
2. Change the IP address of Authentication Manager which you got backup at step 2.
3. Restore the backup data which you got step 1.