# Restore from snapshot only to warm node?

**URL:** <https://discuss.elastic.co/t/restore-from-snapshot-only-to-warm-node/68636>\
**Category:** Elasticsearch\
**Created:** [December 11, 2016, 7:56am UTC](https://discuss.elastic.co/t/restore-from-snapshot-only-to-warm-node/68636 "2016-12-11T07:56:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arghanil](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@Arghanil](https://discuss.elastic.co/u/Arghanil)\
**Post date:** [December 11, 2016, 7:56am UTC](https://discuss.elastic.co/t/restore-from-snapshot-only-to-warm-node/68636/1 "2016-12-11T07:56:08Z")

</div>

I have hot warm architecture setup in AWS, which is based on instance type (i2 - hot, d2 - warm), and I want to perform a recovery from an old snapshot. I applied index creation template (a common one for all indexes) to have index routing allocation require as d2 type (warm) instance and started restore with include\_global\_state as false so that old index templates (stored with the snapshot) are not given preference. However, shards got allocated evenly across hot and warm nodes.  
After that, I ran curator job to force merge and then allocate the indices to warm nodes, which initiated the process and started moving the shards to the warm nodes.

How does the currently applied index templates work in case of snapshot recovery with include\_global\_state set as false?

---

<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:** [January 8, 2017, 7:56am UTC](https://discuss.elastic.co/t/restore-from-snapshot-only-to-warm-node/68636/2 "2017-01-08T07:56:08Z")

</div>

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