# Best way to make a consistent copy of data

**URL:** <https://discuss.elastic.co/t/best-way-to-make-a-consistent-copy-of-data/322418>\
**Category:** Elasticsearch\
**Created:** [January 4, 2023, 4:27am UTC](https://discuss.elastic.co/t/best-way-to-make-a-consistent-copy-of-data/322418 "2023-01-04T04:27:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ankh](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ankh](https://discuss.elastic.co/u/ankh)\
**Post date:** [January 4, 2023, 4:27am UTC](https://discuss.elastic.co/t/best-way-to-make-a-consistent-copy-of-data/322418/1 "2023-01-04T04:27:04Z")

</div>

I have a system containing billions of documents. I have a requirement to have a consistent point in time copy of a subset of fields from 1 year's worth of data (eg 200M documents). The documents are subject to change, in the order of a small fraction of the documents involved, but enough to be concerned about having an assured consistent, complete copy of the data "frozen" for future reference. The copy will be used by another system, and kept to provide evidence for why the other system produced its output.

The options I can think of are:

1. Extract the data from Elastic and write to another permanent store that will use this data.
2. Snapshot the data within Elastic.

For (1) I guess something like point-in-time is the way to ensure consistency? We are running 6.2.3 and so don't have access to features like this, so I suppose we would have to risk inconsistency.

For (2) we would still need to extract the data to a permanent store as the Elastic store is not truly permanent for us. However I'm not sure if I understand the snapshot process in terms of data consistency correctly.

What would be the best way to achieve this?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 4, 2023, 7:03am UTC](https://discuss.elastic.co/t/best-way-to-make-a-consistent-copy-of-data/322418/2 "2023-01-04T07:03:16Z")

</div>

You could also [clone the index](https://www.elastic.co/guide/en/elasticsearch/reference/8.5/indices-clone-index.html).

> [@ankh](#):
>
> We are running 6.2.3

_Very old_ and very [EOL](https://www.elastic.co/support/eol). You would get a tonne of benefit from upgrading asap.

---

<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:** [February 1, 2023, 7:03am UTC](https://discuss.elastic.co/t/best-way-to-make-a-consistent-copy-of-data/322418/3 "2023-02-01T07:03:52Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.