Radius replication server restore fails during DB reload

[DavidBeitler]

Am running a test DR scenario, so am creating a new VM instance and attempting to restore the database, but is failing at the "RADIUS restore" section.  The DB is from a system running 8.1 SP1 Patch 5, with a primary and a replica.  The new VM instance is a single primary instance.  I seem to recall having this issue before.  And I believe it has something to do with RADIUS replication, and not having a secondary in the new setup.   Does anyone know what the procedure is for getting past this?.

[DavidBeitler]

The test system does come up, but there is not radius information in the SC "You need to accurately configure a RADIUS server before you can view..."

Connection to RADIUS server failed due to incorrect credentials.

[EdwardDavis]

Is the target FQDN the same as the source that made the backup ? If so see KB 000033001

[DavidBeitler]

Cannot seem to find that KB.  I have another system, that was running patch 6, and it did not manifest this problem.

I also made a point of configuring the OC user name and password on the new system to be the same as that from the imported DB.

The rest of the import was successful, just the radius component fails.

[DavidBeitler]

Just noticed:

On the production system, the host name is rsa-host-01.xxx.com

On the test system, the host name is rsa-host01.xxx.com

On the test system, in the OC, and looking at the Radius server, it lists the production host name, but the test system IP.

Any suggestions?

[DavidBeitler]

Sorry, not seeing clearly this morning, the test system actually lists the host name and IP of the production system. 

[DavidBeitler · Accepted solution]

Was able to resolve the issues after much KB searching

KB 00026352, DOC-45314

Seems that having an agent record in the import DB with the same name/IP as the test AM server caused the problem.  Changed the IP and hostname of the test AM server and the restore completed successfully.