High availability and disaster recovery

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

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

Related documentation:
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?
Telemetry Service N = N (N+1) Active-spare Primary or secondary unit

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


For High Availability and Load Balancing, Telemetry Service implements an N+1 architecture available behind a Load Balancer.

Telemetry Service is deployed in all Engage Multicloud region/data center so that a client application like WWE can always find a Telemetry Service region/data center where it is relocated.

Retrieved from "https://all.docs.genesys.com/TLM/Current/TLMPEGuide/HADR (2021-12-05 07:45:21)"