github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 09:48:58 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Adds note about backups to Upgrade doc (#50525) (#50723)

Browse source 
* [DOCS] Adds note about backups to Upgrade doc

* [DOCS] Incorporates review comments in upgrade doc

* [DOCS] Fixes typo
This commit is contained in:
gchaps 2019-11-14 12:52:49 -08:00 • committed by GitHub
parent 5e8c6cf8a6
commit ceec158876
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/setup/upgrade.asciidoc
View file

@ -2,7 +2,15 @@
== Upgrading {kib}
Depending on the {kib} version you're upgrading from, the upgrade process to 7.0
varies.
varies.
NOTE: {kib} upgrades automatically when starting a new version, as described in
<<upgrade-migrations, this document>>.
Although you do not need to manually back up {kib} before upgrading, we recommend
that you have a backup on hand. You can use
<<snapshot-repositories, Snapshot and Restore>> to back up {kib}
data by targeting `.kibana*` indices. If you are using the Reporting plugin,
you can also target `.reporting*` indices.
[float]
[[upgrade-before-you-begin]]
@ -12,7 +20,7 @@ Before you upgrade {kib}:
* Consult the <<breaking-changes,breaking changes>>.
* Before you upgrade production servers, test the upgrades in a dev environment.
* Backup your data with {es} {ref}/modules-snapshots.html[snapshots].
* Back up your data with {es} {ref}/modules-snapshots.html[snapshots].
To roll back to an earlier version, you **must** have a backup of your data.
* If you are using custom plugins, check that a compatible version is
available.