Due to maintenance activity on VMWare, we need to shutdown our primary instance for 4 hrs. I know we can't perform administrative activities during this time as primary is down and we are fine to buy this time with a change ticket. Need help on understanding below during this activity.
- We have 4 replicas in our deployment. Replicas servers will be active and complete authentications for users?
- What will be the status of replication in replica server?
- Will this have any impact on Authentication Agents, Radius clients or any application protected using RSA AM?
- Post maintenance activity, if we start the primary instance, does replication will start automatically and function normally?
Nishanth Shaga,
While your primary is down, your replica servers will pick up the authentication requests from your end users, that is the whole point of having multiple authentication servers
The primary will show as Instance Offline. Replication may show as out of synch while the primary is down but that is to be expected since the replica(s) cannot communicate with the primary. Once the primary is back online, replication status should return to normal.
It should not. Any authentication requests from your agents, RADIUS clients and other apps protected by Authentication Manager will work without impact. Before the primary is taken offline, you may want to check the authentication activity logs and confirm that the agents, clients, etc. have authenticated not only to the primary but also to the replica server(s) to verify the requests will go to the other servers.
Once you restart the primary, it will communicate with your replicas. The replica servers will send their authentication logs and other information to the primary. The primary will then share that information amongst all replicas so they are all aware of authentications that happened, PIN changes, etc.
Regards,
Erica