High availability and disaster recovery

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

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.
NameHigh AvailabilityDisaster RecoveryWhere can you host this service?
Genesys CX Insights N = 2 (active-active) Not supported Primary unit only
Reporting and Analytics Aggregates Not supported Not supported

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


By default, GCXI provides High Availability support using StatefulSets with 2 x Pods in Active-Active mode, which form a MicroStrategy cluster. GCXI does not support autoscaling. High Availability is not applicable to RAA.

GCXI does not support Disaster Recovery or any kind of cross-regional deployment. In most scenarios, GCXI is deployed in customer's primary region only. If GCXI is deployed in supplementary regions, each such deployment is completely independent from each other. Pods in different regions do not communicate with each other.

Multi-region availability[ | edit source]

Functionality Pattern Design Dependencies Limitation Activate Activate Time Rollback Rollback Time Changes
GCXI Pilot-Light GCXI deployed in the primary region. The DB and File storage are replicated to secondary region. GIM DB must be available in the secondary region None
  • If needed teardown GCXI in primary region
  • Change secondary region replicated DB and File storage to R/W and have them replicated to primary region (if available)
  • Deploy GCXI in secondary region using the replicated DB and File storage
  • Notify tenant to use the secondary GCXI tile in Portal
under 15 mins
  • Teardown secondary region GCXI with a pipeline.
  • Deploy GCXI in primary region
    • If the DB and File storage is replicated to primary region, change to R/W and have replicated to secondary region
    • If the DB and File storage is not replicated to primary region, recreate them using backup data from the secondary region.
  • Update URL for GCXI
under 15 mins Change the GCXI pipeline to convert replicated DB and File Storage to R/W and deploy GCXI

Make sure the Postgres DB is replication across regions

Change the File storage to GZRS Azure files to do replication of the data

  • Reports themselves - email or link
  • Cube - in memory - refreshes on period basis. All the links

Add secondary GCXI tile to Portal pipeline

Regional failover support[ | edit source]


Primary Region failure[ | edit source]

Functionality Operational Impact RepresentativeĀ  Experience Customer Experience
GCXI without GCXI functionality 15 mins No Impact No Impact

Secondary Region Failure[ | edit source]

Functionality Operational Impact RepresentativeĀ  Experience Customer Experience
GCXI No Impact No Impact No Impact

Data Sovereignty and Regulations[ | edit source]

Functionality Design Changes Investigations
GCXI There is potential sensitive data in the reports TBD
Retrieved from "https://all.docs.genesys.com/PEC-REP/Current/GCXIPEGuide/HADR (2021-12-05 07:47:30)"