# Index Backup scheme for Local Machine

**URL:** <https://discuss.elastic.co/t/index-backup-scheme-for-local-machine/5503>\
**Category:** Elasticsearch\
**Created:** [October 3, 2011, 2:07pm UTC](https://discuss.elastic.co/t/index-backup-scheme-for-local-machine/5503 "2011-10-03T14:07:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kartavya](https://avatars.discourse-cdn.com/v4/letter/k/65b543/32.png) [@Kartavya](https://discuss.elastic.co/u/Kartavya)\
**Post date:** [October 3, 2011, 2:07pm UTC](https://discuss.elastic.co/t/index-backup-scheme-for-local-machine/5503/1 "2011-10-03T14:07:22Z")

</div>

Hi,

I saw "time machine" functionality of Elasticsearch and it is awesome.  
But In my implementation I have pretty large amount of data 1 terabyte in 15  
days and it keep on expanding.  
Can you please suggest any index backup scheme that is as good as S3 time  
machine?

Thanks

Regards,  
Pulkit Agrawal

On Mon, Oct 3, 2011 at 7:21 PM, frazer [frazer.horn@gmail.com](mailto:frazer.horn@gmail.com) wrote:

> From what i've read ([Home - Apache Lucene (Java) - Apache Software Foundation](http://wiki.apache.org/lucene-java/)  
> LuceneFAQ#Can\_I\_filter\_by\_score.3F) filtering by score is not a good  
> idea in lucene.
> 
> I was wondering if there are any other options other than the  
> min\_score filter in Elastic that would make doing something like this  
> more viable. I'm thinking along the lines of using scripting with the  
> doc score and max score, but im not sure if this is possible?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:52am UTC](https://discuss.elastic.co/t/index-backup-scheme-for-local-machine/5503/2 "2017-07-06T03:52:59Z")

</div>

Closed on July 6, 2017, 3:52am UTC