Skip to content

Commit

Permalink
docs(self-managed): clarify restore steps (#3491)
Browse files Browse the repository at this point in the history
* docs(self-managed): clarify restore steps

* style(formatting): technical review

* removed incorrect additional step 9

---------

Co-authored-by: Christina Ausley <[email protected]>
  • Loading branch information
johanwelgemoed and christinaausley authored Mar 27, 2024
1 parent e9f7c36 commit 64fbfcd
Show file tree
Hide file tree
Showing 5 changed files with 40 additions and 20 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,11 @@ If any of the steps above fail, you may have to restart with a new backup id. En

To restore a Camunda 8 cluster from a backup, all components must be restored from their backup corresponding to the same backup id:

1. Restore the state of [Operate](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/operational-guides/backup-restore/optimize-backup.md).
2. Restore `zeebe-records*` indices from Elasticsearch snapshot.
3. Restore [Zeebe](/self-managed/operational-guides/backup-restore/zeebe-backup-and-restore.md).
4. Start Zeebe, Operate, Tasklist, and Optimize.
1. Start Zeebe, Operate, Tasklist, and Optimize. (To ensure templates/aliases etc. are created)
2. Confirm proper configuration (such as shards, replicas count, etc.)
3. Stop Operate, Tasklist, and Optimize.
4. Delete all indices.
5. Restore the state of [Operate](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/operational-guides/backup-restore/optimize-backup.md).
6. Restore `zeebe-records*` indices from Elasticsearch snapshot.
7. Restore [Zeebe](/self-managed/operational-guides/backup-restore/zeebe-backup-and-restore.md).
8. Start Zeebe, Operate, Tasklist, and Optimize.
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,11 @@ If any of the steps above fail, you may have to restart with a new backup id. En

To restore a Camunda 8 cluster from a backup, all components must be restored from their backup corresponding to the same backup id:

1. Restore the state of [Operate](/self-managed/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/backup-restore/optimize-backup.md).
2. Restore `zeebe-records*` indices from Elasticsearch snapshot.
3. Restore [Zeebe](self-managed/backup-restore/zeebe-backup-and-restore.md).
4. Start Zeebe, Operate, Tasklist, and Optimize.
1. Start Zeebe, Operate, Tasklist, and Optimize. (To ensure templates/aliases etc. are created)
2. Confirm proper configuration (such as shards, replicas count, etc.)
3. Stop Operate, Tasklist, and Optimize.
4. Delete all indices.
5. Restore the state of [Operate](/self-managed/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/backup-restore/optimize-backup.md).
6. Restore `zeebe-records*` indices from Elasticsearch snapshot.
7. Restore [Zeebe](self-managed/backup-restore/zeebe-backup-and-restore.md).
8. Start Zeebe, Operate, Tasklist, and Optimize.
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,11 @@ If any of the steps above fail, you may have to restart with a new backup id. En

To restore a Camunda 8 cluster from a backup, all components must be restored from their backup corresponding to the same backup id:

1. Restore the state of [Operate](/self-managed/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/backup-restore/optimize-backup.md).
2. Restore `zeebe-records*` indices from Elasticsearch snapshot.
3. Restore [Zeebe](self-managed/backup-restore/zeebe-backup-and-restore.md).
4. Start Zeebe, Operate, Tasklist, and Optimize.
1. Start Zeebe, Operate, Tasklist, and Optimize. (To ensure templates/aliases etc. are created)
2. Confirm proper configuration (such as shards, replicas count, etc.)
3. Stop Operate, Tasklist, and Optimize.
4. Delete all indices.
5. Restore the state of [Operate](/self-managed/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/backup-restore/optimize-backup.md).
6. Restore `zeebe-records*` indices from Elasticsearch snapshot.
7. Restore [Zeebe](self-managed/backup-restore/zeebe-backup-and-restore.md).
8. Start Zeebe, Operate, Tasklist, and Optimize.
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,11 @@ If any of the steps above fail, you may have to restart with a new backup id. En

To restore a Camunda 8 cluster from a backup, all components must be restored from their backup corresponding to the same backup id:

1. Restore the state of [Operate](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/operational-guides/backup-restore/optimize-backup.md).
2. Restore `zeebe-records*` indices from Elasticsearch snapshot.
3. Restore [Zeebe](/self-managed/operational-guides/backup-restore/zeebe-backup-and-restore.md).
4. Start Zeebe, Operate, Tasklist, and Optimize.
1. Start Zeebe, Operate, Tasklist, and Optimize. (To ensure templates/aliases etc. are created)
2. Confirm proper configuration (such as shards, replicas count, etc.)
3. Stop Operate, Tasklist, and Optimize.
4. Delete all indices.
5. Restore the state of [Operate](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/operational-guides/backup-restore/optimize-backup.md).
6. Restore `zeebe-records*` indices from Elasticsearch snapshot.
7. Restore [Zeebe](/self-managed/operational-guides/backup-restore/zeebe-backup-and-restore.md).
8. Start Zeebe, Operate, Tasklist, and Optimize.
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,11 @@ If any of the steps above fail, you may have to restart with a new backup id. En

To restore a Camunda 8 cluster from a backup, all components must be restored from their backup corresponding to the same backup id:

1. Restore the state of [Operate](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/operational-guides/backup-restore/optimize-backup.md).
2. Restore `zeebe-records*` indices from Elasticsearch snapshot.
3. Restore [Zeebe](/self-managed/operational-guides/backup-restore/zeebe-backup-and-restore.md).
4. Start Zeebe, Operate, Tasklist, and Optimize.
1. Start Zeebe, Operate, Tasklist, and Optimize. (To ensure templates/aliases etc. are created)
2. Confirm proper configuration (such as shards, replicas count, etc.)
3. Stop Operate, Tasklist, and Optimize.
4. Delete all indices.
5. Restore the state of [Operate](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), [Tasklist](/self-managed/operational-guides/backup-restore/operate-tasklist-backup.md), and [Optimize](/self-managed/operational-guides/backup-restore/optimize-backup.md).
6. Restore `zeebe-records*` indices from Elasticsearch snapshot.
7. Restore [Zeebe](/self-managed/operational-guides/backup-restore/zeebe-backup-and-restore.md).
8. Start Zeebe, Operate, Tasklist, and Optimize.

0 comments on commit 64fbfcd

Please sign in to comment.