-
Notifications
You must be signed in to change notification settings - Fork 5
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
Validate backup strategies #308
Comments
We just want to observe that the backups exist the way we expect |
Off the top of my head, our Elasticsearch backup strategy: We're using ES incremental snapshots. Current policy: Backups to
Future policy: Backup to
cc @thepsalmist for any additional context/correction. |
Created the B2 repositories |
B2 backups failed and needed to be retried for this most recent period- eventually the upload succeeded. -per @kilemensi |
Let's run a test restore of the ILM, using the B2 backups. |
Elasticsearch's Restore API allows to perform various restorations from a snapshot, including Restoring an index, or restoring an entire cluster.
The existing index stats are as follows
Index mc_search-000002 - 2TB
To do any of the index's restore to a different cluster, we'd need minimum disk storage of 0.8TB |
Does ☝🏽 mean none of the current servers have such a capacity @thepsalmist? |
Yes none |
Ok., so the options for a restore then are:
|
No description provided.
The text was updated successfully, but these errors were encountered: