Replica Instance
A replica instance provides deployment-level redundancy of the primary instance. With a few exceptions, you can view, but not update, administrative data on a replica instance.
A replica instance provides the following benefits:
Real-time mirror of all user and system data
Failover authentication if the primary instance becomes unresponsive
Improved performance by load balancing authentication requests to multiple instances
Ability to deploy a replica instance at a remote location
Ability to recover administrative capabilities through replica promotion if the primary instance becomes unresponsive
Administrators can clear PINs and provide emergency access to users
Note: If the primary instance has an “Out-of-Sync” replication status, for any reason, resynchronizing the deployment removes any administrative changes that occurred on a replica instance. For example, you may need to regenerate an offline emergency access tokencode that was generated on a replica instance.
Although a replica instance is optional, RSA recommends that you deploy both a primary and a replica instance. The RSA Authentication Manager Base Server license and the Enterprise Server license both include permission to deploy a replica instance.
Related Articles
Replica Instance Promotion for Disaster Recovery 123Number of Views Replica Instance Synchronization 101Number of Views Synchronize a Replica Instance 74Number of Views Promote a Replica Instance Using Promotion for Maintenance 446Number of Views Promotion for maintenance fails: Unable to apply the data updates from the primary instance 292Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators