# Snapshot completed with success but archive creation failed

**URL:** <https://discuss.elastic.co/t/snapshot-completed-with-success-but-archive-creation-failed/253866>\
**Category:** Elasticsearch\
**Created:** [October 30, 2020, 9:15pm UTC](https://discuss.elastic.co/t/snapshot-completed-with-success-but-archive-creation-failed/253866 "2020-10-30T21:15:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alita](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@alita](https://discuss.elastic.co/u/alita)\
**Post date:** [October 30, 2020, 9:15pm UTC](https://discuss.elastic.co/t/snapshot-completed-with-success-but-archive-creation-failed/253866/1 "2020-10-30T21:15:20Z")

</div>

Hi folks,

I created a snapshot using the following curl command:  
`curl -X PUT "localhost:9200/_snapshot/my_backup/snapshot_1?wait_for_completion=true&pretty"`

After the snapshot completed with success, I execute a simple tar command to create an archive:  
`tar cvzf backup.tgz -C /snapshots/my_backup .`

My concern is that, from time to time, I receive the following error:

> tar: .: file changed as we read it

I'm trying to understand what I can do to cover this corner case, in order to have an e2e process working.

Thank you.

---

<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 27, 2020, 9:15pm UTC](https://discuss.elastic.co/t/snapshot-completed-with-success-but-archive-creation-failed/253866/2 "2020-11-27T21:15:49Z")

</div>

Closed on November 27, 2020, 9:15pm UTC

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