问题描述
我正在编写SonarQube管理的内部手册，但是在将ElasticSearch引擎加入产品后，我无法解决这个问题.在此之前，数据库备份并复制了一些足以保存SQ状态的文件夹，但是现在使用ElasticSearch应该怎么做?
I'm writing an internal manual for SonarQube administration but after getting ElasticSearch engine into the product I have not been able to close the circle. Before this, a DB backup and copy some folders where enough to save SQ status, but what should I do now with ElasticSearch?
是否应该仅使用ES的另一个节点，以便实时复制索引?我应该复制新的节点分片并将其保留为备份吗?如果需要，如何恢复SQ状态?
Should I simply use one more node of ES so to have a live duplicate of indexes? Should I make a copy of the new node shards and keep it as backup?And how can I restore the SQ status if required?
推荐答案
无需备份ElasticSearch索引，SonarQube会在需要时重新创建它.基本上，如果您需要还原数据库备份，则:
No need to backup the ElasticSearch index, SonarQube will re-create it if needed. Basically, if you need to restore a DB backup then:
- 停止SonarQube
- 清除 sonar_install_dir/es 下的现有索引
- 还原数据库备份
- 重新启动SonarQube
- stop SonarQube
- wipe-out the existing index under sonar_install_dir/es
- restore your DB backup
- restart SonarQube
到那时，SonarQube将自动重新创建索引(可能需要一些时间，具体取决于数据量).
At that point SonarQube will automatically re-create the index (may take some time depending on volume of data).
这篇关于使用ElasticSearch的SonarQube备份还原过程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！