# Clone index API vs. Scan and Scroll API

**URL:** <https://discuss.elastic.co/t/clone-index-api-vs-scan-and-scroll-api/288311>\
**Category:** Elasticsearch\
**Created:** [November 3, 2021, 9:45am UTC](https://discuss.elastic.co/t/clone-index-api-vs-scan-and-scroll-api/288311 "2021-11-03T09:45:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![madshov](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@madshov](https://discuss.elastic.co/u/madshov)\
**Post date:** [November 3, 2021, 9:45am UTC](https://discuss.elastic.co/t/clone-index-api-vs-scan-and-scroll-api/288311/1 "2021-11-03T09:45:21Z")

</div>

Hi,  
What's the better way to create a clone of my index for reindex purposes? Use the clone API or the scroll API and then bulk index? What are the pro and cons of each method?

---

<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:** [November 4, 2021, 12:13am UTC](https://discuss.elastic.co/t/clone-index-api-vs-scan-and-scroll-api/288311/2 "2021-11-04T00:13:12Z")

</div>

I'd suggest either the clone API, or snapshot and restore (if you are already taking backups).

The clone API should be most efficient.

---

<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:** [December 2, 2021, 12:13am UTC](https://discuss.elastic.co/t/clone-index-api-vs-scan-and-scroll-api/288311/3 "2021-12-02T00:13:22Z")

</div>

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