保存多年来的Elasticsearch快照 - 最佳政策和实践
我们正在使用Elasticsearch V7.10，并希望在我们的群集中添加快照策略。我们希望即使几年后也能够恢复特定的索引。
一方面，建议频繁拍摄快照（〜每30分钟 - 设置快照策略），但另一方面，积累数千个快照并不是最好的做法，因为它需要更多的内存，因为它需要更多的内存在主节点上可以使其不稳定。建议将保留规则包括在SLM策略中（快照保留限制）。
在过去的7年中，我需要能够从每个月的每个月恢复至少1个快照 - 有可能吗？我的SLM政策/IES和保留规则应该如何？
We are using Elasticsearch v7.10 and want to add a snapshot policy to our cluster. We want to be able to restore specific indexes even after few years.
On the one hand it is recommended to take frequent snapshots (~every 30 minuets - Set up snapshot policy) but on the other hand it is not a best practice to accumulate thousands of snapshots, because it requires more memory on the master node and can destabilize it. It is recommended to include retention rules in the SLM policy (Snapshot retention limits).
I need to be able to restore at least 1 snapshot from each month in the last 7 years - is it possible? how does my SLM policy/ies and retention rules should look like?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
首先，更新Elasticsearch，并尽可能保持最新。 8.x现在是当前的，而7.x仅在7.16级别进行修补。但是您是7.10，该7.10在2020年后期发布
，您可能需要多个SLM政策。因此，您可以使用更频繁地丢弃的较短快照，而与每月用于长期保留要求相比，
您可以考虑为每月快照制作年度快照存储库需要
firstly, update Elasticsearch, and keep as up to date as you can. 8.X is now current and 7.X is only patched at the 7.16 level. but you're on 7.10, which was released in (late) 2020
second, you might want more than one slm policy. so something that you can use to take shorter snapshots that are discarded more frequently, versus monthly ones that you use for long term retention requirements
you can then look at making yearly snapshot repositories for the monthly snapshots, that means you can easily drop repos you don't need