This page was last edited on August 5, 2014, at 17:59.
Comments or questions about this documentation? Contact us for support!
Disaster Recovery scenarios may result in loss of some reporting data, for two main reasons:
As discussed further in Info Mart Database Replication, certain tables, which are mostly internal, are not replicated to the standby database. Excluding these tables from replication optimizes network bandwidth utilization between the sites and replication performance during day-to-day operations; however, this setup implies that a subset of the Info Mart tables do not have identical data between the two sites. Because the subset of tables that are excluded from replication do not contain the data used in reports, unavailability of data from these tables does not constitute data loss.
For information about potential data loss that network connectivity issues may cause during normal two-site operation, see Note on Connectivity Loss.
A site failure results in termination of any calls that are active at the failed site at the moment of failure. The reporting data about these calls will not be available. Similarly, data about any agent states that are active at the time of a site failure will be lost.
When a site failure occurs, reporting data for some of the recent contact-center activities may not be complete because extraction, transformation, or replication is likely to be interrupted by the failure.
Extraction of data for any given time period is a one-time operation: Genesys Info Mart does not re-extract data for a time period that has already been extracted. After a site failure, the newly active Genesys Info Mart will not re-extract the data that the failed Genesys Info Mart had previously extracted. This design, which is intended to improve performance, brings a risk of reporting data being lost during Disaster Recovery.
In essence, any data that has not been delivered to the standby Info Mart database by the time of the disaster event may be lost.
The time that it takes to replicate the processed data to the standby database also plays a role in data availability. Under certain circumstances, delay in data replication may result in the standby Info Mart database having an earlier high-water mark than the active database has for extracted data. In this case, Genesys Info Mart that is brought into service at Site 2 can potentially extract from the redundant IDB at Site 2 a subset of data that was previously extracted from the Site 1 IDB.