Skip to content

Update restore-snapshot.md #2183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update restore-snapshot.md #2183

wants to merge 1 commit into from

Conversation

jaebongim
Copy link

HI, Team.
In order to restore the kibana session index, the Kibana instance must be terminated before deletion and restoration are possible. So I added the relevant part.
I would appreciate it if you could reflect it in the document after checking it.

HI, Team.
In order to restore the kibana session index, the Kibana instance must be terminated before deletion and restoration are possible.
So I added the relevant part.
I would appreciate it if you could reflect it in the document after checking it.
Copy link

🔍 Preview links for changed docs

Copy link
Contributor

@eedugon eedugon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a few minor suggestions.

I prefer to not specify .kibana* system indices, as now Kibana data is restored through feature states.

@@ -306,13 +306,15 @@ If you’re restoring to a different cluster, see [Restore to a different cluste
DELETE _data_stream/*?expand_wildcards=all
```

6. Delete all existing indices on the cluster.
6. Shutdown All Kibana (important, especially if you plan to restore .kibana* system indices).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
6. Shutdown All Kibana (important, especially if you plan to restore .kibana* system indices).
6. Stop all {{kib}} instances connected to the cluster. This is an important step, especially if you plan to restore {{kib}} data.

@@ -322,7 +324,9 @@ If you’re restoring to a different cluster, see [Restore to a different cluste
}
```

8. When the restore operation is complete, resume indexing and restart any features you stopped:
9. Restart All Kibana
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
9. Restart All Kibana
9. Start all {{kib}} instances

@eedugon
Copy link
Contributor

eedugon commented Jul 21, 2025

@jaebongim : Do you have confirmation from devs or your own tests about stopping Kibana being needed in order to restore kibana data or the entire cluster?

I'd say in the past it was probably required, but not sure how it works today with the feature states.

eedugon

This comment was marked as duplicate.

@eedugon eedugon self-requested a review July 21, 2025 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants