# Metricbeat 6.3.2 upgrade breaks?

**URL:** <https://discuss.elastic.co/t/metricbeat-6-3-2-upgrade-breaks/142241>\
**Category:** Beats\
**Created:** [July 30, 2018, 6:59pm UTC](https://discuss.elastic.co/t/metricbeat-6-3-2-upgrade-breaks/142241 "2018-07-30T18:59:28Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![json](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/json/32/4125_2.png) [@json](https://discuss.elastic.co/u/json)\
**Post date:** [February 28, 2019, 3:43pm UTC](https://discuss.elastic.co/t/metricbeat-6-3-2-upgrade-breaks/142241/10 "2019-02-28T15:43:58Z")

</div>

I should be more specific about what happens here. The old Metricbeat template causes new data to have the wrong mapping. If preserving data is required, then these steps should work:

1. place a write block on the "bad" `metricbeat-<version>.*` index with `index.blocks.write: true`
2. delete the old template
3. reindex the bad index it to an index with a different name
4. delete the bad index

The new Metricbeat will then be free to index to `metricbeat-<version>` without a mapping conflict.

---

_[View the full topic](https://discuss.elastic.co/t/metricbeat-6-3-2-upgrade-breaks/142241)._