# Backup/Restore Indexes **URL:** \ **Category:** Elasticsearch\ **Created:** [January 4, 2024, 8:22pm UTC](https://discuss.elastic.co/t/backup-restore-indexes/350411 "2024-01-04T20:22:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![marcowiskhy](https://avatars.discourse-cdn.com/v4/letter/m/5f9b8f/32.png) [@marcowiskhy](https://discuss.elastic.co/u/marcowiskhy)\ **Post date:** [January 4, 2024, 8:22pm UTC](https://discuss.elastic.co/t/backup-restore-indexes/350411/1 "2024-01-04T20:22:16Z")
Hey guys, I have an Elasticsearch node in production and am experiencing issues regarding disk storage. At the moment I cannot increase computational resources or add other nodes because I depend on collaboration with another department in the company. As a temporary measure to avoid stopping the cluster, can I somehow perform a backup/dump of some indexes to another server, and then restore them later? ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [January 4, 2024, 8:31pm UTC](https://discuss.elastic.co/t/backup-restore-indexes/350411/2 "2024-01-04T20:31:25Z")
The easiest way would be to create some snapshots on a cloud service and after that you could remove the local indices. Using the Snapshot/Restore API is the only officially supported way of backup Elasticsearch data. Here is the [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshot-restore.html). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 1, 2024, 8:32pm UTC](https://discuss.elastic.co/t/backup-restore-indexes/350411/3 "2024-02-01T20:32:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.