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

Jump to bottom

docs: backup/restore strategy #62

Open

slint opened this issue Jun 26, 2018 · 0 comments · May be fixed by #109

Assignees

Member

slint commented Jun 26, 2018 •

edited

Loading

The only copy of the raw events is stored in the index, so in case of an ElasticSearch cluster failure/loss, the events will be lost.

There are various solutions in terms of backing up ES:

ES Snapshots
elasticdump
Raw filesystem backups for each node... 🤢

In terms of managing indices it might be also worth taking a look into the Python library elasticsearch-curator.

(TODO: add some numbers from Invenio instances running invenio-stats for what's the estimated number of events/storage used)

The text was updated successfully, but these errors were encountered:

topless self-assigned this

topless linked a pull request

that will close this issue

docs: backup & restore ES #109

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment