Skip to content

Update elastic-cloud-hosted-planning.md #6775

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.

Sign up for GitHub

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
nclough wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update elastic-cloud-hosted-planning.md #6775

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,9 @@
Clusters that use only one availability zone are not highly
available and are at risk of data loss. To safeguard against data loss,
you must use at least two availability zones.

Note: Snapshots do not restore all configurations (e.g., custom repositories).

Check warning on line 46 in deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md

View workflow job for this annotation

GitHub Actions / build / vale 

Elastic.Latinisms: Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
Review the full [snapshot contents](https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore#snapshot-contents) list to understand recovery limitations.
Comment on lines +46 to +47
Copy link
Copy Markdown
Member

@shainaraskas shainaraskas Jun 2, 2026

Choose a reason for hiding this comment

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

this note doesn't make sense to be embedded in this warning. I think it would make more sense integrated into line 39 where we have the other snapshot-related limitations.

We also need to use a relative link instead of an absolute one: /deploy-manage/tools/snapshot-and-restore.md#snapshot-contents

The data in your {{es}} clusters is also backed up every 30 minutes, 4 hours, or 24 hours, depending on which snapshot interval you choose. These regular intervals provide an extra level of redundancy. We do support snapshot and restore, regardless of whether you use one, two, or three availability zones. However, with only a single availability zone and in the event of an outage, it might take a while for your cluster come back online. Using a single availability zone also leaves your cluster exposed to the risk of data loss, if the backups you need are not usable (failed or partial snapshots missing the indices to restore) or no longer available by the time that you realize that you might need the data (snapshots have a retention policy). In addition, snapshots do not capture all configurations, which can lead to an incomplete recovery.

::::


Expand Down
Loading