# Upgrade breaks config

**URL:** <https://discuss.elastic.co/t/upgrade-breaks-config/269405>\
**Category:** Elasticsearch\
**Created:** [April 7, 2021, 6:25am UTC](https://discuss.elastic.co/t/upgrade-breaks-config/269405 "2021-04-07T06:25:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![viper539](https://avatars.discourse-cdn.com/v4/letter/v/7ba0ec/32.png) [@viper539](https://discuss.elastic.co/u/viper539)\
**Post date:** [April 7, 2021, 6:25am UTC](https://discuss.elastic.co/t/upgrade-breaks-config/269405/1 "2021-04-07T06:25:49Z")

</div>

Hello Friends,  
maybe i'm doing it wrong sind years...  
Can anyone tell me where i can put my individual config and keep it safe during an upgrade?

Every time, when i upgrade my ELK, the process tries to overwrite my elasticsearch.yml with default settings. It tries to remove the cluster settings, the IP and so on....

Oh, yes. There is a /etc/default/elasticsearch...  
Same here. I put there my NodeName and other things, and after every upgrade i can set this again.

Same for FileBeat, Metricbeat, Kibana...

I cannot beleive that this is the "normal" way.

Thank you,  
Viper

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 7, 2021, 6:53am UTC](https://discuss.elastic.co/t/upgrade-breaks-config/269405/2 "2021-04-07T06:53:41Z")

</div>

The "normal" way is documented here: [Upgrade Elasticsearch | Elasticsearch Guide [7.12] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 7, 2021, 8:13am UTC](https://discuss.elastic.co/t/upgrade-breaks-config/269405/3 "2021-04-07T08:13:54Z")

</div>

Welcome to our community! 😃

This is standard linux behaviour, but you should also be able to tell your package manager to ignore changes in the new packages.

---

<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:** [May 5, 2021, 8:14am UTC](https://discuss.elastic.co/t/upgrade-breaks-config/269405/4 "2021-05-05T08:14:50Z")

</div>

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