Camunda 8.7 Backup & Restore

[Preethis]

Hey Team,

I am currently on Camunda 8.7 Self Managed On AKS.

Is the below approach recommended with the backups in production. Using Azure Storage Blob

Elastic search backup includes all indices with single API

Zeebe backup for Zeebe Cluster

Restore.

ES Snapshot restore

Zeebe restore.

I do see the documentation has individual components backup not entire elastic search backup for operate / task list/ zeebe-record / optimize with * as including all indices. Also i noticed in documentation while restoring there is an instruction to delete the pvc.

Pl let me know if I should proceed with approach or if I get detailed instruction would be helpful.

[zee-bot]

Your approach needs refinement - simply taking Elasticsearch snapshots with all indices isn’t recommended as it doesn’t ensure consistency across Camunda components, and each component (Operate, Tasklist, Optimize) must be backed up through their built-in APIs using the same backup ID. I found the following relevant resources:

• Camunda backup creation (Elasticsearch/OpenSearch)
• Why you should use backup and restore APIs
• Camunda back up and restore guide
• Restore a backup
• Production data safety best practices
• PVC deletion and data loss considerations

Does this help? If not, can anyone from the community jump in?

---

Hints: Use the Ask AI feature in Camunda’s documentation to chat with AI and get fast help. Report bugs and features in Camuda’s GitHub issue tracker. Trust the process.

[Preethis]

Do we have custom scripts available for restore? Do we really need to delete the pvc while doing the restore procedure.

@zee-bot