# Restore backup taken from other elasticsearch to new one

**URL:** <https://discuss.elastic.co/t/restore-backup-taken-from-other-elasticsearch-to-new-one/302867>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [April 21, 2022, 4:08am UTC](https://discuss.elastic.co/t/restore-backup-taken-from-other-elasticsearch-to-new-one/302867 "2022-04-21T04:08:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Blason](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/blason/32/42284_2.png) [@Blason](https://discuss.elastic.co/u/Blason)\
**Post date:** [April 21, 2022, 4:08am UTC](https://discuss.elastic.co/t/restore-backup-taken-from-other-elasticsearch-to-new-one/302867/1 "2022-04-21T04:08:17Z")

</div>

Hi Team,

I have a elastic stack where the indices backup is taken on s3 bucket and it around 5 TB of data. I am planning to copy it to another S3 bucket and will be installing fresh elastic stack.  
Wondering if I can restore the data by connecting same s3? What do I need to do for restoring?

TIA  
Blason R

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [April 21, 2022, 4:39am UTC](https://discuss.elastic.co/t/restore-backup-taken-from-other-elasticsearch-to-new-one/302867/2 "2022-04-21T04:39:36Z")

</div>

Yes you can register a read only repository that already exist, pretty common way to snap and restore to a new cluster.

Make sure you look close a the docs / correct version and version compatibility matrix.

> **[Register a snapshot repository | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html)**

> If you register the same snapshot repository with multiple clusters, only one cluster should have write access to the repository. On other clusters, register the repository as read-only.
> 
> This prevents multiple clusters from writing to the repository at the same time and corrupting the repository’s contents. It also prevents Elasticsearch from caching the repository’s contents, which means that changes made by other clusters will become visible straight away.

---

<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 19, 2022, 4:40am UTC](https://discuss.elastic.co/t/restore-backup-taken-from-other-elasticsearch-to-new-one/302867/3 "2022-05-19T04:40:16Z")

</div>

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