# Curator Snapshot and S3 file name **URL:** \ **Category:** Elasticsearch\ **Created:** [May 25, 2017, 9:21pm UTC](https://discuss.elastic.co/t/curator-snapshot-and-s3-file-name/87185 "2017-05-25T21:21:44Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![\_sar](https://avatars.discourse-cdn.com/v4/letter/_/ac8455/32.png) [@\_sar](https://discuss.elastic.co/u/_sar)\ **Post date:** [May 25, 2017, 9:21pm UTC](https://discuss.elastic.co/t/curator-snapshot-and-s3-file-name/87185/1 "2017-05-25T21:21:44Z")
I have curator configured and working properly by taking snapshots and sending them to a bucket in S3. What I can't seem to understand is how to have the filename in S3 match the snapshot name specified in the config file which I can clearly see when I run: '\_cat/snapshots/s3\_repo?v' the name of the snapshot is the one specified in my config file, however when I look at my s3 bucket, the filename for the .dat file appears to be saved as meta- followed by a random string. Is there some setting I need to add in the curator config to specify the name of the output file and not just the name of the snapshot? ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [May 25, 2017, 11:28pm UTC](https://discuss.elastic.co/t/curator-snapshot-and-s3-file-name/87185/2 "2017-05-25T23:28:19Z")
This is how newer versions of Elasticsearch do it. Indices are also named similarly. The snapshot name is only in the metadata, accessible via API call. ---
**Author:** ![\_sar](https://avatars.discourse-cdn.com/v4/letter/_/ac8455/32.png) [@\_sar](https://discuss.elastic.co/u/_sar)\ **Post date:** [May 26, 2017, 3:52pm UTC](https://discuss.elastic.co/t/curator-snapshot-and-s3-file-name/87185/3 "2017-05-26T15:52:06Z")
Aaron, Thanks for the info and was wondering whether you can expand a bit more on that as I'm trying to understand exactly what files I'm supposed to be seeing in the S3 bucket for a successful snapshot. I see files with meta-random\_string and one with snap-random\_string and there's also an index-(number) and I also believe there's an indices folder ... So, just wanting to have a very clear picture of what a typical snapshot should generate. Thanks for the help. ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [May 26, 2017, 4:20pm UTC](https://discuss.elastic.co/t/curator-snapshot-and-s3-file-name/87185/4 "2017-05-26T16:20:30Z")
You're better off using the [API](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html) to validate that snapshots were correctly taken. A successful snapshot will have `state: SUCCESS`. ```auto GET /_snapshot/REPO_NAME/_all ``` However, Curator provides a [CLI tool](https://www.elastic.co/guide/en/elasticsearch/client/curator/5.0/singleton-cli.html) and a [filter](https://www.elastic.co/guide/en/elasticsearch/client/curator/5.0/filtertype_state.html) to check the `state` of snapshots: ```auto curator_cli --host 127.0.0.1 --port 9200 show_snapshots --repository REPO_NAME --filter_list '[{"filtertype":"state","state":"SUCCESS"}]' ``` If you have a client config file in `~/.curator/curator.yml` then `curator_cli` will auto detect it, and all you would need to run is: ```auto curator_cli show_snapshots --repository REPO_NAME --filter_list '[{"filtertype":"state","state":"SUCCESS"}]' ``` or you can point it to the config file with `--config` ```auto curator_cli --config /path/to/curator_config.yml show_snapshots --repository REPO_NAME --filter_list '[{"filtertype":"state","state":"SUCCESS"}]' ``` What will output is a list of all snapshots which were successful. ---
**Author:** ![\_sar](https://avatars.discourse-cdn.com/v4/letter/_/ac8455/32.png) [@\_sar](https://discuss.elastic.co/u/_sar)\ **Post date:** [May 26, 2017, 4:33pm UTC](https://discuss.elastic.co/t/curator-snapshot-and-s3-file-name/87185/5 "2017-05-26T16:33:37Z")
Aaron, Yeah I ran all that after reading the docs and as previously stated, I verified that the snapshot succeeded by running some of the commands you mention. However, I'm just curious to know more about the structure of the files generated with a successful snapshot as I haven't come across much on that. ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [May 26, 2017, 4:37pm UTC](https://discuss.elastic.co/t/curator-snapshot-and-s3-file-name/87185/6 "2017-05-26T16:37:55Z")
They are segments, and files that help organize them and catalog them so Elasticsearch can easily see what's there. We recommend these files _never_ be touched directly, so you won't find any documentation about them. If you really want to know what's up there, you will have to peruse the code. I won't be making any recommendations other than what I have. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 23, 2017, 4:37pm UTC](https://discuss.elastic.co/t/curator-snapshot-and-s3-file-name/87185/7 "2017-06-23T16:37:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.