# Restore Incremental

**URL:** <https://discuss.elastic.co/t/restore-incremental/129327>\
**Category:** Elasticsearch\
**Created:** [April 24, 2018, 2:44pm UTC](https://discuss.elastic.co/t/restore-incremental/129327 "2018-04-24T14:44:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bitva77](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitva77/32/66694_2.png) [@bitva77](https://discuss.elastic.co/u/bitva77)\
**Post date:** [April 24, 2018, 2:44pm UTC](https://discuss.elastic.co/t/restore-incremental/129327/1 "2018-04-24T14:44:32Z")

</div>

Hi! I'm in the process of migrating our ES cluster from Windows to Docker/Linux. I thought I could do it with Snapshots/Restore.

This partially works but not really.

Our cluster is like 4TB in size. A snapshot takes like 4 hours to do out to disk. Similarly with restoring.

Which I thought was find with snapshot\_1. I took a snapshot\_2 which is in incremental and so took much quicker to complete but I can't resotre it as I'm told:

`cannot restore index [usage-2017.06] because an open index with same name already exists in the cluster. Either close or delete the existing index or restore the index under a different name by providing a rename pattern and replacement name`

Is the only way to restore 4TB of data would be to do all 4TB in one go? Is there no way to restore an incremental?

I'm assuming I'm missing something 🙂 Thanks so much!

-Matt

---

<div class="post-metadata">

**Author:** ![bitva77](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitva77/32/66694_2.png) [@bitva77](https://discuss.elastic.co/u/bitva77)\
**Post date:** [April 24, 2018, 4:06pm UTC](https://discuss.elastic.co/t/restore-incremental/129327/2 "2018-04-24T16:06:24Z")

</div>

If I'm reading the documentation correctly, if I close all indexes in the destination cluster and then I attempt to restore snapshot\_2 (after restoring snapshot\_1), it'll open the ones that were open in the source cluster, correct? (having include\_global\_state = true)

In essence, restoring an incremental onto an existing cluster. That right?

---

<div class="post-metadata">

**Author:** ![bitva77](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitva77/32/66694_2.png) [@bitva77](https://discuss.elastic.co/u/bitva77)\
**Post date:** [April 24, 2018, 9:47pm UTC](https://discuss.elastic.co/t/restore-incremental/129327/3 "2018-04-24T21:47:43Z")

</div>

think I answered my own question by doing it. I think I'm good now.

Thanks for being my thought board 🙂

---

<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:** [May 22, 2018, 9:47pm UTC](https://discuss.elastic.co/t/restore-incremental/129327/4 "2018-05-22T21:47:44Z")

</div>

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