What is the difference between deployment of session failover and deployment of multiple Access Manager servers?
Session failover in Access Manager retains the authenticated session state in case of a hardware or software failure of a single server. Failover provides both infrastructure redundancy (no single point of failure) and state redundancy (no information loss in the existing sessions after failure). Unlike session failover, deployment of multiple Access Manager servers ensures only the continuation of service availability for new sessions.
Related Questions
- In the case of multiple Access Manager servers with session failover enabled, what happens if the session validation request lands in a server that does not hold the session?
- In the configuration for session failover, whats the relationship among the policy agents, the Load Balancer, and the Access Manager servers behind Load Balancers?
- What is the difference between deployment of session failover and deployment of multiple Access Manager servers?