ECH no backups of found-snapshots#7212
Open
stefnestor wants to merge 2 commits into
Open
Conversation
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
🔍 Preview links for changed docs |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Contributor
There was a problem hiding this comment.
Docs review summary
Focus areas
- Style and clarity: One actionable finding on the new bullet — see inline comment. The sentence has a vague subject ("All changes made"), awkward phrasing ("reset to earlier time periods"), and a discouraged modal ("should"). Suggested replacement provided inline.
- Jargon: "cloud host level backups" is Elastic-internal phrasing that external users may not recognize; "host-level backups" is clearer and more universal.
- Frontmatter and
applies_to: No frontmatter changes in this PR. Pre-existing missingdescriptionfield not introduced here. - Content type fit: Adding a considerations bullet is well-suited to this page.
- Parent issue satisfaction: The PR's stated goal — documenting that Elastic does not take host-level backups of
found-snapshotsand that deletions are permanent — is addressed by the new bullet. The inline suggestion tightens the phrasing without changing the meaning.
Generated by Docs review agent for issue #7212 · 42.3 AIC · ⌖ 8.32 AIC · ⊞ 10.7K
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Speaking towards an infrequent high severity question, this delineates that for our built-in ECH
found-snapshots, Elastic does not by default enable that some cloud hosts allow you to do backups of the data directory. And we don't do that (as would increase billing). So if users delete their (searchable) snapshots, that is a permanent deletion in our eyes and also was self-inflicted. Users can compensate for this by having backup redundancies.Generative AI disclosure