# Backup ElasticSearch data using GCS unexpectedly crashed

**URL:** <https://discuss.elastic.co/t/backup-elasticsearch-data-using-gcs-unexpectedly-crashed/235162>\
**Category:** Elasticsearch\
**Created:** [June 1, 2020, 12:37pm UTC](https://discuss.elastic.co/t/backup-elasticsearch-data-using-gcs-unexpectedly-crashed/235162 "2020-06-01T12:37:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ab\_Avramidis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ab_avramidis/32/51514_2.png) [@Ab\_Avramidis](https://discuss.elastic.co/u/Ab_Avramidis)\
**Post date:** [June 1, 2020, 12:37pm UTC](https://discuss.elastic.co/t/backup-elasticsearch-data-using-gcs-unexpectedly-crashed/235162/1 "2020-06-01T12:37:03Z")

</div>

Hi,

I had set up ES automatically to make backup of the indices to a Google Cloud Storage repo.  
Everything was working fine until unexpectedly crashed.  
I executed the command `"elasticsearch-keystore list"`to list the available keys for the service account that I use to store the indices into the bucket and is missing.

Does anyone knows how and why the json key was deleted without human intervention?  
Is there any life-cycle period for the keys?  
Anyone with similar experience on the same incident?

My ES version based on the curl -XGET 'localhost:9200' output is:

```
"version" : {
    "number" : "6.4.0"

```

Thanks!

---

<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:** [June 29, 2020, 12:37pm UTC](https://discuss.elastic.co/t/backup-elasticsearch-data-using-gcs-unexpectedly-crashed/235162/2 "2020-06-29T12:37:12Z")

</div>

Closed on June 29, 2020, 12:37pm UTC

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