Skip to content
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.

Commit

Permalink
Merge pull request #2749 from sirensolutions/issue-2716
Browse files Browse the repository at this point in the history
Added a note to backup the .kibiaccess index on upgrades
  • Loading branch information
fabiocorneti committed Apr 25, 2017
2 parents 5f196d0 + f259a03 commit 1cd5a02
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions docs/upgrade.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@
An existing Kibi installation can be upgraded as follows:

- backup the `.kibi` index.
- backup the `.kibiaccess` index if Kibi ACL is enabled.
- backup the Kibi configuration file (`config/kibi.yml`)
- {elastic-ref}setup-upgrade.html[upgrade Elasticsearch]; before restarting each node, make sure to install a compatible version of the
{siren-join-website}#compatibility[SIREn Join] plugin.
Expand Down Expand Up @@ -36,6 +37,8 @@ kibi_core:
Before upgrading it is strongly recommended to have a backup of the `.kibi` index; the recommended way to perform regular backups of
Elasticsearch indexes is through the {elastic-ref}modules-snapshots.html[snapshot and restore modules].

If Kibi ACL is enabled, include the `.kibiaccess` index in the backup.

A useful tool to take a one-off backup is https://www.npmjs.com/package/elasticdump[elasticdump]; once installed, it is possible to dump
the `.kibi` index mappings and data on two separate files by running the following commands:

Expand Down

0 comments on commit 1cd5a02

Please sign in to comment.