diff --git a/docs/self-managed/operational-guides/backup-restore/backup-and-restore.md b/docs/self-managed/operational-guides/backup-restore/backup-and-restore.md
index cc02762e01a..618e069adfb 100644
--- a/docs/self-managed/operational-guides/backup-restore/backup-and-restore.md
+++ b/docs/self-managed/operational-guides/backup-restore/backup-and-restore.md
@@ -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.
diff --git a/versioned_docs/version-8.1/self-managed/backup-restore/backup-and-restore.md b/versioned_docs/version-8.1/self-managed/backup-restore/backup-and-restore.md
index eff01ac67b0..772ef78a771 100644
--- a/versioned_docs/version-8.1/self-managed/backup-restore/backup-and-restore.md
+++ b/versioned_docs/version-8.1/self-managed/backup-restore/backup-and-restore.md
@@ -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.
diff --git a/versioned_docs/version-8.2/self-managed/backup-restore/backup-and-restore.md b/versioned_docs/version-8.2/self-managed/backup-restore/backup-and-restore.md
index 6d94530e05c..9e55b7c3ceb 100644
--- a/versioned_docs/version-8.2/self-managed/backup-restore/backup-and-restore.md
+++ b/versioned_docs/version-8.2/self-managed/backup-restore/backup-and-restore.md
@@ -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.
diff --git a/versioned_docs/version-8.3/self-managed/operational-guides/backup-restore/backup-and-restore.md b/versioned_docs/version-8.3/self-managed/operational-guides/backup-restore/backup-and-restore.md
index e15cc1f9354..e0003e4bd79 100644
--- a/versioned_docs/version-8.3/self-managed/operational-guides/backup-restore/backup-and-restore.md
+++ b/versioned_docs/version-8.3/self-managed/operational-guides/backup-restore/backup-and-restore.md
@@ -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.
diff --git a/versioned_docs/version-8.4/self-managed/operational-guides/backup-restore/backup-and-restore.md b/versioned_docs/version-8.4/self-managed/operational-guides/backup-restore/backup-and-restore.md
index e15cc1f9354..e0003e4bd79 100644
--- a/versioned_docs/version-8.4/self-managed/operational-guides/backup-restore/backup-and-restore.md
+++ b/versioned_docs/version-8.4/self-managed/operational-guides/backup-restore/backup-and-restore.md
@@ -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.