Introducing an hourly backup schedule minimizes data loss, enhances disaster recovery, ensures compliance with regulations, provides operational flexibility, and significantly improves data protection and business continuity strategies. Hourly backups will significantly decreases Recovery Time Objective (RTO), facilitating quicker operational restoration.
User Problem
Not having hourly backup intervals can lead to significant data loss in dynamic environments, regulatory industry compliance issues, operational inefficiencies, and challenges in capturing time-sensitive data. It limits disaster recovery planning flexibility.
Release Notes
TBD
User Stories
[x] As a Camunda 8 administrator, I want to schedule backups to occur on an hourly basis, so that we can minimize data loss and ensure fast operational recovery
[x] As a Camunda 8 SRE, I want to enable backup configurations to be set per organization within our platform so that we can limit hourly backup availability so that we can manage stability of our system and gradually introduce backup to all organizations over time (perhaps we can use console limit)
Implementation Notes
Make sure that backups are sequential (in controller) camunda-cloud/camunda-operator/issues/1687
This is dependent on the resilience of the backup epic (otherwise we have too many failing backups)
Ideally, ZDP team has completed "to not pause exporter epic" by then.
Double-check Cloud Storage and make sure we do not run into issues.
We assume Statig can be used to limit customer rollout
We need to control backup creation and make sure only a single backup is running
:robot: This issue is automatically synced from: source
Value Proposition Statement
Introducing an hourly backup schedule minimizes data loss, enhances disaster recovery, ensures compliance with regulations, provides operational flexibility, and significantly improves data protection and business continuity strategies. Hourly backups will significantly decreases Recovery Time Objective (RTO), facilitating quicker operational restoration.
User Problem
Not having hourly backup intervals can lead to significant data loss in dynamic environments, regulatory industry compliance issues, operational inefficiencies, and challenges in capturing time-sensitive data. It limits disaster recovery planning flexibility.
Release Notes
TBD
User Stories
Implementation Notes
Make sure that backups are sequential (in controller) camunda-cloud/camunda-operator/issues/1687
This is dependent on the resilience of the backup epic (otherwise we have too many failing backups)
Ideally, ZDP team has completed "to not pause exporter epic" by then.
Double-check Cloud Storage and make sure we do not run into issues.
We assume Statig can be used to limit customer rollout
We need to control backup creation and make sure only a single backup is running
:robot: This issue is automatically synced from: source