title: Elasticsearch hot-backup strategies
body: <p>It would be interesting if someone could share his best 'hot-backup' strategies for <code>ElasticSearch</code>.</p>
  
  <p>Also, feel free to share tools and libraries related to this problem and can help. </p>
  
  <p><strong>Updated:</strong>
  Thank you @javanna for your response, it's quite complete and provides good direction for further actions.</p>
  
  <p>I also did a small research and found some articles/discussions which can help if somebody has an interest.</p>
  
  <ul>
  <li><a href="http://www.dark.ca/2011/11/22/elasticsearch-backup-strategies/">Elasticsearch backup strategies</a></li>
  <li><a href="http://tech.superhappykittymeow.com/?p=296">Backup/restore Elasticsearch index</a> and <a href="https://gist.github.com/1939828">related snippet on github:gist</a></li>
  <li><a href="http://elasticsearch-users.115913.n3.nabble.com/Elastic-Search-Backup-and-Recovery-td4020442.html">Elastic Search Backup and Recovery</a> discussion (check the comment of Paul Smith, also he shared a usefull link to his <a href="https://github.com/Aconex/scrutineer">tool for verifying indexes</a> )</li>
  </ul>
  
  <p><strong>Update:</strong> Elasticsearch 1.0 have an "official" backup solution - <a href="http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-snapshots.html">Snapshot/Restore API</a> and this is the only right way to it now. ElasticSearch will identify master shards and take care about consistency. The backup is going to be done incrementally, so you will be able to do it very fast and as often as you want.</p>