2016-10-25 18:24:24 +02:00
[[upgrade-standard]]
2019-04-03 20:50:47 +02:00
=== Standard upgrade
2016-10-25 18:24:24 +02:00
2020-06-08 23:46:26 +02:00
NOTE: 6.7 includes an https://www.elastic.co/guide/en/kibana/6.7/upgrade-assistant.html[Upgrade Assistant]
to help you prepare for your upgrade to 7.0. To access the assistant, go to *Management > 7.0 Upgrade Assistant*.
2016-10-25 18:24:24 +02:00
2019-04-03 20:50:47 +02:00
[IMPORTANT]
===========================================
If you've saved and/or exported objects in {kib} that rely on the
<<search,Elasticsearch Query DSL>>, make sure to check the {es}
2017-06-27 19:13:42 +02:00
{ref}/breaking-changes.html[breaking changes] documentation and take the
2016-10-25 18:24:24 +02:00
necessary remediation steps as per those instructions.
2019-04-03 20:50:47 +02:00
===========================================
2016-10-25 18:24:24 +02:00
2020-10-27 17:31:36 +01:00
[float]
==== Upgrading multiple {kib} instances
2021-01-25 15:36:48 +01:00
NOTE: Kibana does not support rolling upgrades. If you're running multiple {kib} instances, all instances should be stopped before upgrading.
2020-10-27 17:31:36 +01:00
2021-01-25 15:36:48 +01:00
Different versions of {kib} running against the same {es} index, such as during a rolling upgrade, can cause data loss. This is because older instances will continue to write saved objects in a different format than the newer instances. To prevent this from happening ensure that all old {kib} instances are shutdown before starting up instances on a newer version.
2020-10-27 17:31:36 +01:00
2016-10-25 18:24:24 +02:00
[float]
2020-06-08 23:46:26 +02:00
==== Upgrade using a `deb` or `rpm` package
2016-10-25 18:24:24 +02:00
2019-04-03 20:50:47 +02:00
. Stop the existing {kib} process using the appropriate command for your
2021-01-25 15:36:48 +01:00
system. If you have multiple {kib} instances connecting to the same {es}
cluster ensure that all instances are stopped before proceeding to the next
step to avoid data loss.
2016-10-25 18:24:24 +02:00
. Use `rpm` or `dpkg` to install the new package. All files should be placed in
their proper locations and config files should not be overwritten.
+
[NOTE]
--
2019-04-03 20:50:47 +02:00
{kib} 4.x used a different config location than 5.0+, so if you're upgrading
2016-10-25 18:24:24 +02:00
from 4.x, you will need to copy the configurations from your old config
(`/opt/kibana/config/kibana.yml`) to your new config
(`/etc/kibana/kibana.yml`).
Make sure you remove or update any configurations
that are indicated in the <<breaking-changes,breaking changes>> documentation
2019-04-03 20:50:47 +02:00
otherwise {kib} will fail to start.
2016-10-25 18:24:24 +02:00
--
. Upgrade any plugins by removing the existing plugin and reinstalling the
appropriate version using the `kibana-plugin` script. Check out the
<<kibana-plugins,plugins>> documentation for more information.
2019-04-03 20:50:47 +02:00
. Start the new {kib} process using the appropriate command for your system.
2016-10-25 18:24:24 +02:00
[float]
2020-06-08 23:46:26 +02:00
==== Upgrade using a `zip` or `tar.gz` archive
2016-10-25 18:24:24 +02:00
. Extract the `zip` or `tar.gz` archive to a new directory to be sure that you
2018-03-14 21:18:53 +01:00
don't overwrite the `config` or `data` directories. +
+
--
2020-10-27 17:31:36 +01:00
IMPORTANT: If you use {monitor-features}, you must re-use the data directory when you upgrade {kib}. Otherwise, the {kib} instance is assigned a new persistent UUID
2018-03-14 21:18:53 +01:00
and becomes a new instance in the monitoring data.
--
2016-10-25 18:24:24 +02:00
. Copy the files from the `config` directory from your old installation to your
new installation. Make sure you remove or update any configurations that are
indicated in the <<breaking-changes,breaking changes>> documentation
2019-04-03 20:50:47 +02:00
otherwise {kib} will fail to start.
2016-10-25 18:24:24 +02:00
. Copy the files from the `data` directory from your old installation to your
new installation.
. Install the appropriate versions of all your plugins for your new
installation using the `kibana-plugin` script. Check out the
<<kibana-plugins,plugins>> documentation for more information.
2021-01-25 15:36:48 +01:00
. Stop the old {kib} process. If you have multiple {kib} instances connecting
to the same {es} cluster ensure that all instances are stopped before
proceeding to the next step to avoid data loss.
2019-04-03 20:50:47 +02:00
. Start the new {kib} process.