# A second/third .kibana index is created after each upgrade
**URL:** https://discuss.elastic.co/t/a-second-third-kibana-index-is-created-after-each-upgrade/206771
**Category:** Kibana
**Created:** [November 6, 2019, 10:09am UTC](https://discuss.elastic.co/t/a-second-third-kibana-index-is-created-after-each-upgrade/206771 "2019-11-06T10:09:08Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Kuckkuck](https://discuss.elastic.co/u/Kuckkuck)
#### Post date: [November 6, 2019, 10:09am UTC](https://discuss.elastic.co/t/a-second-third-kibana-index-is-created-after-each-upgrade/206771/1 "2019-11-06T10:09:08Z")
Hi,
any idea, what I did wrong? After each upgrade for example from 5 - 6 , from 6.8 -\> 7.3.2 , 7.3.2 -\> 7.4.0 I get another nice .kibana\_x index created. Nicely numbered one of another. Some have data, some not. Any idea, why this is happening? I am normally deleting the oldest one, so only one is left which has the alias. Now with 7.4.0 the .kibana\_task\_manager\_x is also doubled.... Any idea, why this is happening?
Thanks a lot
Olaf
---
### Author:  [@Aaron\_Caldwell](https://discuss.elastic.co/u/Aaron_Caldwell)
#### Post date: [November 7, 2019, 9:36pm UTC](https://discuss.elastic.co/t/a-second-third-kibana-index-is-created-after-each-upgrade/206771/2 "2019-11-07T21:36:56Z")
Hello Olaf,
Preserving the old index but updating the `.kibana` alias is done by design. Here's [some background](https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html#upgrade-migrations-old-indices) on this process.
Regards,
Aaron
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 5, 2019, 9:36pm UTC](https://discuss.elastic.co/t/a-second-third-kibana-index-is-created-after-each-upgrade/206771/3 "2019-12-05T21:36:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.