Revision as of 14:24, May 23, 2018 by Pmcknigh (talk | contribs) (Created page with "=Disaster Recovery / Business Continuity= This section describes a recommended architecture to ensure successful disaster recovery, or business continuity, following a scenari...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Disaster Recovery / Business Continuity

This section describes a recommended architecture to ensure successful disaster recovery, or business continuity, following a scenario in which the main site was rendered inoperable because of some natural or other disaster.

Overview

The Genesys system configuration is stored in a single database, and can be accessed by only one primary master Configuration Server connection at a time. The Configuration Database is constantly modified by Configuration Server clients, and is archived periodically to prevent the loss of data. However, database maintenance and periodic backup can cause significant downtime. It cannot prevent partial or whole loss of configuration data if a major disaster occurs, such as one in which the Configuration Database and all updates and modifications made since the last backup is completely lost. To improve the robustness of the Management Framework solution and to reduce downtime for system maintenance, this architecture replicates a secondary standby database.

Architecture

The following diagram illustrates the disaster recovery architecture for a multi-site configuration operating under normal conditions.

MF851 Dep DR-BC-arch.png
Comments or questions about this documentation? Contact us for support!