High availability and disaster recovery

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Genesys Callback Private Edition Guide for version Current of Callback.

Find out how this service provides disaster recovery in the event the service goes down.

Early Adopter Program
Genesys Multicloud CX private edition is being released to pre-approved customers as part of the Early Adopter Program. Please note that the documentation and the product are subject to change. For more details about the program, please contact your Genesys representative.
Service High Availability Disaster Recovery Where can you host this service?
Genesys Engagement Service N = N (N+1) Not supported Primary unit only

This information is under development: Flagged items aren't yet confirmed or have info coming soon; Checked items are valid.


See High Availability information for all services: High availability and disaster recovery


Genesys Engagement Service (GES) uses automated failure recovery mechanisms that allow GES to try to recover from critical failure scenarios such as a node failure or a partial or full Redis failure. The following sections illustrate how these failure recovery processes work.

GES node failure[ | edit source]

The following diagram depicts the automated recovery procedures when one of the GES nodes goes offline.

Ges pe gesnode failover diagram.png

Partial Redis failure[ | edit source]

The following diagram depicts the automated recovery procedures when the primary Redis node goes offline.

Ges pe partialredis failover diagram.png

Full Redis failure[ | edit source]

The following diagram depicts the automated recovery procedures when both the primary and replica Redis nodes go offline.

Ges pe fullredis failover diagram.png
Retrieved from "https://all.docs.genesys.com/PEC-CAB/Current/CABPEGuide/HADR (2021-11-27 09:37:29)"