High availability and disaster recovery

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

Related documentation:

• Suite-level guide
• All services
• Designer Release Notes

RSS:

• For private edition

Name	High Availability	Disaster Recovery	Where can you host this service?
Designer	N = N (N+1) Or N = 2 (active-active)	Pilot light	Primary unit only
Designer Application Server	N = N (N+1) Or N = 2 (active-active)	Active-spare	Primary or secondary unit

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

Designer and DAS must be deployed as highly available in order to avoid single points of failure. A minimum of 2 replicas of each service must be deployed to achieve HA.

The Designer and DAS service pods can be automatically scaled up or down based on metrics such as CPU and memory utilization. The Deployment configuration settings section provides more information on configuring HA and auto-scaling.

Important

The pilot-light DR or multi-region pattern for the Designer service is supported only for the primary region.

Refer to the Genesys Docker Deployment Guide for more information on general HA recommendation for Kubernetes.