Camunda 8.10 introduces cross-region disaster recovery for supported Camunda 8 Software as a Service (SaaS) region pairs. Camunda Hub Console manages backup replication and recovery, so teams can restore a cluster in a secondary region if the primary region becomes unavailable.
This gives SaaS customers a Camunda-supported recovery capability that Self-Managed customers have traditionally had to design and maintain themselves.
Consider a claims process running on Camunda 8 SaaS: new claims arrive, automated checks run, and adjusters complete tasks. If the region hosting the cluster goes down, your team needs to answer three questions:
- Where can we recover?
- How much recent process data could we lose?
- What will it take to resume processing?
A backup protects process data, but regional recovery also requires an accessible place to restore it and a procedure your team can follow during an outage. Cross-region disaster recovery brings more of that work into Hub Console, reducing the infrastructure and recovery tooling your team needs to manage.
You configure a supported secondary region for your production cluster. Console then manages three parts of the recovery process:
- Tracks backups created by the primary cluster.
- Replicates backup data to the secondary region.
- Provisions and restores a cluster from any available backup when you initiate recovery.
The restored cluster reflects a saved point in time. Changes made after that recovery point may need to be reconciled with your source systems before normal processing resumes.
For the claims process, this means identifying submissions, task completions, and external actions that occurred after the backup's recovery point. Restoring the cluster is one part of recovery; ensuring that its state is consistent with the surrounding business systems is another.
Camunda offers a dedicated failover backup schedule with intervals ranging from every 15 minutes to hourly, daily, weekly, and monthly. Choose a schedule based on how much recent process data your business can afford to lose or reconstruct. A high-volume transaction process may need more frequent backups than an internal approvals process.
Two objectives help define your recovery requirements:
- Recovery point objective (RPO): The amount of recent data loss your business can tolerate, measured in time.
- Recovery time objective (RTO): The length of time your business can tolerate the service being unavailable.
A 15-minute backup schedule does not guarantee a 15-minute RPO. A backup must finish and reach the secondary region before it can be used for recovery. Backup frequency also does not determine how long provisioning and restoration will take.
Choose a schedule that supports your business requirements, then validate that the recovery procedure can meet them.
Initial support covers these region pairs:
- Ohio and Oregon
- Ohio and Northern Virginia
- Iowa and South Carolina
Additional region pairs are on the roadmap. Before planning a rollout, confirm that your cluster has a supported secondary region and that the destination meets your organization's data residency requirements. If the pairing you need is unavailable, discuss it with your account team.
For customers using bring-your-own-key (BYOK) with AWS, the necessary encryption keys must also be available in the secondary region. Include key availability in your readiness checks: replicated backups are usable only if they can be decrypted at the recovery destination.
Documents and other process-related object storage are outside the scope of this feature's replication. If a process depends on uploaded evidence, attachments, or generated documents, restoring the cluster alone may not be enough to resume work.
Your recovery plan must account for those files. Some may be retrievable from source systems or regenerated; others may need a separate replication or backup strategy. Establish how each will be recovered before an outage.
Before relying on cross-region disaster recovery:
- Confirm that your source and destination regions are supported and meet your data residency requirements.
- Choose a backup schedule that fits your data-loss tolerance.
- Check backup replication readiness and, where applicable, BYOK replication status.
- Document how applications, workers, integrations, and stored documents will be made available during recovery.
- Assign responsibility for initiating recovery and reconciling process data.
- Validate the recovery procedure against your RPO and RTO requirements.
Camunda is built for mission-critical operations, and the same resilience that keeps long-running processes moving now extends to regional recovery. A recovery capability is part of the trust, governance, and control those operations demand, and it requires an operational plan that business owners, operations teams, and auditors can assess before an incident occurs.
Cross-region disaster recovery is available now for supported Camunda 8 SaaS region pairs. To put it into practice, select a recovery destination, configure backups, and test the steps your team will take to resume processing. See the disaster recovery setup guide to configure a secondary region, or talk to your account team to confirm the pairing you need.