home

Reltio

ReltioProductsDeveloper resourcesRolesApplicationsObjectives
ReltioProductsDeveloper resourcesRolesApplicationsObjectives

Unify and manage your data

Show Contents

thumbnailReltio

Reltio Business Critical Edition

Manage disaster recovery with Business Critical Edition

Learn how Reltio Business Critical Edition manages disaster recovery.

Business Critical Edition provides cross-region redundancy by maintaining mirrored tenant pairs (development, test, and production) across two cloud regions. The mirrored region is maintained as a warm standby, ready to take over operations if the primary region becomes unavailable.

During a disaster recovery event, covered services continue to operate from the mirrored region with minimal disruption, maintaining data integrity and availability within defined RPO and RTO targets.

This enables a controlled transition between regions to support business continuity without requiring manual reconfiguration of your applications.

To manage disaster recovery with Business Critical Edition:
  1. If the Reltio monitoring system detects an incident, or if you report one, the Reltio incident response team conducts an initial assessment to determine the severity and impact of the incident.
  2. Once the incident is qualified as a disaster incident and Reltio executives approve the failover process, Reltio communicates the expected actions and timeline, and provides you with:
    1. Confirmation when the disaster recovery plan is activated
    2. Details of the mirrored region (during setup, you can request these from us)
  3. Reltio initiates a disaster recovery protocol:
    1. Activates the mirrored region.
    2. Transitions the mirrored region from warm standby to active status, enabling full read/write capabilities.
    3. Switches operations from the primary to the mirrored region
  4. You test and verify the operational functionality in the mirrored region to ensure all processes and data are functioning as expected.
    Reltio remains on hand to provide updates and support for any issues you raise until the primary region is restored and deemed stable.
  5. Reltio manages the failback process to ensure data integrity and system performance and informs you of the timing and progress.
  6. You confirm functionality and performance in the primary region before Reltio returns the mirrored region to its warm standby status.

Example disaster recovery scenario

Here's an example of how Business Critical Edition manages disaster recovery:

  1. At 2:00 PM, a failure is detected in the primary data center. Reltio immediately publishes an alert to your organization's designated contact and triages the issue.

  2. By 2:15 PM, Reltio confirms the need to activate the disaster recovery protocol and communicates this to you, providing the details of the mirrored region.

  3. By 2:45 PM, the mirrored region is active, and you begin your verification processes.

  4. You report successful operation in the mirrored region by 3:00 PM, and the system continues to function under the disaster recovery protocol until the primary region is restored.

Note: For RDM tenants on AWS, Business Critical Edition uses the same cross-region disaster recovery model. It replicates RDM data in DynamoDB using Global Tables and synchronizes Elasticsearch indices across regions to support failover.

Updated on April 17, 2026

Footer

You've found your way to a temporary environment. Content is not complete or final. Looking for Reltio documentation? Go to docs.reltio.com.

© 2026 The RELTIO® mark is a registered trademark of Reltio, Inc. in the United States and other countries; DataDriven and Reltio Data Cloud are trademarks of Reltio, Inc. Other names or marks are trademarks of their respective owners.

Terms and Conditions, Privacy Policy, and