# Elastic Search - SnapShot to Azure Blob Failing with StorageException

**URL:** <https://discuss.elastic.co/t/elastic-search-snapshot-to-azure-blob-failing-with-storageexception/147704>\
**Category:** Elasticsearch\
**Created:** [September 7, 2018, 11:55am UTC](https://discuss.elastic.co/t/elastic-search-snapshot-to-azure-blob-failing-with-storageexception/147704 "2018-09-07T11:55:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vijayaram\_boopalan](https://avatars.discourse-cdn.com/v4/letter/v/85f322/32.png) [@vijayaram\_boopalan](https://discuss.elastic.co/u/vijayaram_boopalan)\
**Post date:** [September 7, 2018, 11:55am UTC](https://discuss.elastic.co/t/elastic-search-snapshot-to-azure-blob-failing-with-storageexception/147704/1 "2018-09-07T11:55:04Z")

</div>

I have been using the Elastic Search Cluster for more than a year without any issue, I will be doing regular snapshot backup and deletion of old indices and kept the available disk space on the average for all nodes well below 65%.

Version of Cluster:  
"version\_id": 5060399,  
"version": "5.6.3",

But suddently today i am getting the below error during snapshot

"reason": "IndexShardSnapshotFailedException[Failed to perform snapshot (index files)]; nested: IOException; nested: StorageException[The value for one of the HTTP headers is not in the correct format.

Kindly help me to resolve it

---

<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:** [October 5, 2018, 11:55am UTC](https://discuss.elastic.co/t/elastic-search-snapshot-to-azure-blob-failing-with-storageexception/147704/2 "2018-10-05T11:55:06Z")

</div>

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