Conversation
Initial rdbms documentation
|
👋 🤖 🤔 Hello, @christinaausley! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
panagiotisgts
changed the title
docs/self-managed/operational-guides/backup-restore/react-components/_card-data.js
Outdated
Show resolved
Hide resolved
docs/self-managed/operational-guides/backup-restore/rdbms/backup.md
Outdated
Show resolved
Hide resolved
| With Zeebe being set up against an RDBMS secondary storage, you have the option to enable Zeebe's internal backup scheduler. Enabling the scheduler will result in primary storage backups being | ||
| created at the predefined interval. Learn more about configuring the backup scheduler [here](../../../../components/orchestration-cluster/core-settings/configuration/properties/#camundadataprimary-storagebackup). | ||
|
|
||
| In addition to the scheduler, continuous primary storage backups must be enabled, by setting `camunda.data.primary-storage.backup.continous` to true. With continuous backups enabled, |
There was a problem hiding this comment.
🔧 This is a prerequisite, let's mention it up there
|
@christinaausley let me know if you agree on the general direction of splitting the backup/restore guides for RDBMS and ES/OS, then I'll start adding more content to the RDBMS guide. |
|
@lenaschoenburg -- apologies for the delay. I will have a look at this today 👍 |
|
Mild grammar tweaks in latest commit. Thanks for this update -- I agree with the general direction of splitting ES/OS and RDBMS backup/restore guides. It improves navigation and reduces mixed guidance. From a #7117 perspective (semi-related), this PR is a good step forward 👍 I like the clear separation of Elasticsearch/OpenSearch vs RDBMS procedures, discoverability from the backup/restore overview, and clearer end-to-end flow for each storage path. Remaining gaps (can be handled here or I can handle in a follow-up PR)
For the items below, I’m fine with either brief references in this PR or a separate follow-up to keep scope tight:
|
|
The preview environment relating to the commit 4f3ee41 has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-8087/ |
3 participants
Description
backup & restoreguidesdocs/next/self-managed/operational-guides/backup-restore/backup-and-restore/to reflect the split guidesdocs/next/self-managed/operational-guides/backup-restore/elasticsearch/es-backup/docs/next/self-managed/operational-guides/backup-restore/rdbms/rdbms-backup/When should this change go live?
bugorsupportlabel)available & undocumentedlabel)holdlabel)low priolabel)PR Checklist
{type}(scope): {description}commit message(s)/docsdirectory (version 8.9)./versioned_docsdirectory.@camunda/tech-writersunless working with an embedded writer.