|Applies To||RSA Product Set : SecurID|
RSA Product/Service Type : RSA Authentication Manager
RSA Version/Condition: 8.1 Service Pack 1
Platform : SUSE Enterprise Linux
O/S Version : 11 Service Pack 3
Product Description : SecurID Appliance
|Issue||An administrator has a requirement to restore a production backup into a user acceptance testing (UAT) authentication manager deployment.|
|Resolution||Things to consider when taking a backup and restoring a backup.|
- Schedule Backups create regular backups of the deployment data according to the days and times specified. Administrators can specify where to save these backups and take immediate backups from the Operations Console.
- Backups taken on one version of authentication manager software must be restored into a primary instance using the same version of authentication manager software.
- No administration or authentication operations can be performed while the data is restored into a primary instance. The restore process takes longer to complete than the backup process because the authentication services are stopped and started. The size of the internal database also determines the amount of time required to restore data. If the internal database is large, the process can take a long time.
- A backup that is restored from the original primary instance in the current deployment retains each replica instance and each replica needs to be synchronized with the restored primary.
- If you restored the primary instance with a backup that came from a different deployment, then the restore operation automatically deletes each replica instance from the current deployment.
|Notes||Chapter 15: System Maintenance and Disaster Recovery of the RSA Authentication Manager 8.1 Administrator's Guide (Revision 1) contains information on creating backups and performing primary instance data restoration.|