# Human readable name of Snapshot folder

**URL:** <https://discuss.elastic.co/t/human-readable-name-of-snapshot-folder/89110>\
**Category:** Elasticsearch\
**Created:** [June 12, 2017, 9:10pm UTC](https://discuss.elastic.co/t/human-readable-name-of-snapshot-folder/89110 "2017-06-12T21:10:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sharon.c](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sharon.c/32/16076_2.png) [@sharon.c](https://discuss.elastic.co/u/sharon.c)\
**Post date:** [June 12, 2017, 9:10pm UTC](https://discuss.elastic.co/t/human-readable-name-of-snapshot-folder/89110/1 "2017-06-12T21:10:18Z")

</div>

I am doing snapshot using rest api for my elasticsearch indices, and I want to put the snapshot away for backup  
This is the example of generating a snapshot

```
PUT /_snapshot/index-backups1/snapshot-2017.05.29
{
  "indices": "logstash-2017.05.29",
  "ignore_unavailable": true,
  "include_global_state": false
}

```

I found the snapshot folder is not human readable.

I took 7 snapshots for different indices, and these are the 7 folder names generated  
 ![](https://us1.discourse-cdn.com/elastic/original/3X/a/f/af1b89bce9d81f86ade3a44309665cb016312678.png)

I want to put away snapshots in cheaper storage like AWS Glacier as a daily routine, and later I need to restore some of them. It would be impossible for me to find out the folders and restore when the folder names are not human readable.

Can you provide me a solution for the human readable name of the snapshot?

---

<div class="post-metadata">

**Author:** ![lwintergerst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lwintergerst/32/18164_2.png) [@lwintergerst](https://discuss.elastic.co/u/lwintergerst)\
**Post date:** [June 13, 2017, 6:55pm UTC](https://discuss.elastic.co/t/human-readable-name-of-snapshot-folder/89110/2 "2017-06-13T18:55:54Z")

</div>

Hello Sharon,  
in this case I would recommend you to create a new snapshot repository and then move the whole repository to Glacier instead of just a single index.

The reason why we don't "allow" to move indices is because snapshots are incremental and moving away data would mess with that functionality.

This is what you should do:

1. create new repo
2. do snapshot(s)
3. delete repo in ES (this only removes it from ES, it does not delete the data)
4. move your data

---

<div class="post-metadata">

**Author:** ![sharon.c](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sharon.c/32/16076_2.png) [@sharon.c](https://discuss.elastic.co/u/sharon.c)\
**Post date:** [June 21, 2017, 2:57pm UTC](https://discuss.elastic.co/t/human-readable-name-of-snapshot-folder/89110/3 "2017-06-21T14:57:46Z")

</div>

Thanks for your reply.

---

<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:** [July 19, 2017, 2:58pm UTC](https://discuss.elastic.co/t/human-readable-name-of-snapshot-folder/89110/4 "2017-07-19T14:58:19Z")

</div>

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