Hello Team,
We are planning to create a new setup in new DMZ for 8.4 version.
if i am taking a full backup on old setup which is 8.3 version and deploying it on 8.4 version , will it work and what issues i might run into?
Thanks,
Sumit
Hello Team,
We are planning to create a new setup in new DMZ for 8.4 version.
if i am taking a full backup on old setup which is 8.3 version and deploying it on 8.4 version , will it work and what issues i might run into?
Thanks,
Sumit
Hi Sumit,
The use case of restore of backup from AM 8.3 to AM 8.4 would not work and is not recommended too.
So either you can upgrade your setup running AM 8.3 to AM 8.4 and then take a backup and you can use that backup to restore to the new AM 8.4
(or)
Setup a new AM 8.3 --> Restore the backup to new AM 8.3 and then upgrade to AM 8.4
-Sri
Backup and restore is version specific, and only the exact same patch version that created the backup can import a backup. So, 8.3.0.5.0 can import a backup made from an 8.3.0.5.0, but not from 8.4.0.2.0 or 8.3.0.4.0 for example.
Thanks Ed and Sri for quick response.
This feature to allow older version backups to be imported or restored into newer versions of Authentication Manager - at the strong urging of Customer Support - was on the feature list for AM 8.4, but was scrapped at the last minute due to schedule and other issues. I can't find a Jira Bug associated with this feature, but that is not really important anymore, instead you might want to add this to the RSA Link Authentication Manager Ideas list so it can be voted up but customer.
RSA Ideas for RSA SecurID Access
Everyone in Support will vote for it too.
Backup and restore is version specific, and only the exact same patch version that created the backup can import a backup. So, 8.3.0.5.0 can import a backup made from an 8.3.0.5.0, but not from 8.4.0.2.0 or 8.3.0.4.0 for example.