# Snapshot restore to test server

**URL:** <https://discuss.elastic.co/t/snapshot-restore-to-test-server/253975>\
**Category:** Elasticsearch\
**Created:** [November 2, 2020, 4:34am UTC](https://discuss.elastic.co/t/snapshot-restore-to-test-server/253975 "2020-11-02T04:34:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhuvaneshdct](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhuvaneshdct/32/70081_2.png) [@bhuvaneshdct](https://discuss.elastic.co/u/bhuvaneshdct)\
**Post date:** [November 2, 2020, 4:34am UTC](https://discuss.elastic.co/t/snapshot-restore-to-test-server/253975/1 "2020-11-02T04:34:40Z")

</div>

Im a bit confused about the ES restore process.

I have a prod cluster and stage cluster.

Prod cluster has daily snapshots enabled.

The first time when I restored the snapshot from the prod backup it took a lot more time to restore(due to the size 2TB)

Then the next day prod completed the snapshot(its incremental in nature), so not much changes. Snapshot done in a few mins.

Then on the stage server, I closed the indices and restored the snapshot, this is also quick.

This is what I want to understand. We have done so many changes on the stage server, so I think it has to restore the full data. How it'll identify yesterday's full backup state and only replace them?

---

<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:** [November 30, 2020, 4:35am UTC](https://discuss.elastic.co/t/snapshot-restore-to-test-server/253975/2 "2020-11-30T04:35:04Z")

</div>

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