Accelerate the Value of Data

Manage disaster recovery with Business Critical Edition

Learn how Reltio Business Critical Edition manages disaster recovery.

Your Reltio Business Critical Edition provides cross-region redundancy with mirrored tenant pairs of development, test, and production tenants in two different cloud regions. The mirrored region is maintained as a hot standby — it is fully set up and capable of taking over operations with minimal downtime in case your primary region becomes unavailable due to unforeseen circumstances. This enables a seamless transition between the primary and mirrored regions when necessary to ensure continuous availability and data integrity.

During a disaster recovery incident, Business Critical Edition transitions the mirrored region to read/write mode and pauses replication between the primary and mirrored regions. It automatically scales up compute services in the mirrored region to handle the load until the primary region is restored.

After the disaster recovery incident is resolved, Business Critical Edition initiates a controlled failback procedure. This is based on an agreed point-in-time where the mirrored region may continue to act as the primary until all data and operations are securely transferred back to the original primary site.

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 an 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 mirror region.
    2. Transitions the mirrored region from hot 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 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.